The Fyboard Story
Software should adapt to people. Most enterprise software forces you to change how you work. We believe the tools should bend, not the human. This is the long version of why Fyboard exists.
Chapter I — The Disconnect
Software has gone wrong in two opposite directions. Enterprise giants like SAP and Oracle built the backbone of the global economy, but they were built for an era of bureaucratic control — they dictate workflows instead of adapting to them. Modern SaaS solved usability but created a fragmentation problem: great tools that don't speak the same language. The middle is missing. Individuals outgrow their starter tools while organisations are locked into rigid systems.
Chapter II — The Origin (RCL & Fybyte)
Fyboard was forged on a real construction site — not in a vacuum. Its parent is Raj Corporation Limited (RCL), a ₹4,500 crore EPC company building highways and power transmission in India. Fybyte is RCL's digital arm. When you build concrete that has to hold for forty years, precision is the only option. The same is true of the software that runs it.
Chapter III — The Founder
Fyboard is built by a small focused team — operators first, not consultants. The work began with mapping 532 production tables — the actual record-shaped truths a real EPC company relies on, not the ones a consultant deck assumes.
Chapter IV — The Architecture (one spine, many surfaces)
Fyboard is built on three shared engines: FyBrain (intelligence — extraction, summaries, tagging), Workflow (orchestration — approvals, conditions, audit trails), and FyDrive (files, permissions, versions, lineage). Modules like AlphaCore (contracts), DataBoard (forms), and People (HR) are thin surfaces on top. Improve an engine and every module gets smarter. Everything is connected by default.
Chapter V — The Crucible (2029)
By 2029, Fyboard will replace SAP at RCL completely. Replaced is the precise word — not augmented, not integrated with, not running alongside. If we make it, we have evidence — not opinion — that an engine-first platform can carry the weight of an Indian infrastructure company at scale. If we miss it, we will say so plainly, with the post-mortem published.
Epilogue — The Long Game
Fyboard is not built for a quick exit. It is infrastructure — proven inside RCL first, opening to the world step by step. Whether you're an individual looking for better daily tools or an organisation ready to rethink enterprise systems, you're invited to be part of the story from day one.
For the principles, read /manifesto. For the tighter long-form, read /origin. To apply, visit /careers.
Software should
adapt to people.
Most enterprise software forces you to change how you work. We believe the tools should bend, not the human.
The Two Worlds of Work.
We aren't saying the giants are incompetent. Companies like SAP and Oracle built the backbone of the global economy. But they were built for a different era—one focused on bureaucratic control, not human agility.
They dictate workflows instead of adapting to them. They are trapped by legacy code and shareholder demands.
Then came Modern SaaS. It solved the usability problem but created a fragmentation problem. You have a great tool for files, another for contracts, another for chat. But none of them speak the same language.
"Individuals outgrow their starter tools, while organizations are locked into rigid systems."
Forged in Concrete.
Refined by Code.
Fyboard was born from the chaos of real-world infrastructure. No imaginary problems—just massive scale solutions for our parent entities.
The Builder's Dilemma.
Why would one person take on the giants of enterprise software?
Because the giants forgot who they were building for.
At Raj Corporation Limited (RCL), we paid millions for software that forced us to change how we worked. SAP, Oracle—they build for bureaucracy, assuming the system is right and humans are wrong.
"Software should adapt to people, not force people to adapt to software."
That frustration became an obsession. The only way to get software that respected human workflow was to build it from the ground up—not as features, but as engines.
From Factory Floor to System Design
RCL was concrete, cables, highways, and people. The mess on the ground exposed the gaps in clean software diagrams. When you run infrastructure projects, expecting a rigid ERP to match real work becomes absurd.
The Solo Advantage
In large teams, every decision is a meeting. Solo, every decision is an action. Slow on features, fast on foundations.
"I'm not building for a quick exit. I'm building infrastructure."
Engines, Not Apps
Most tools ship as isolated apps. Fyboard is built as engines first—workflow, documents, people. Apps are just surfaces. Change one engine, propagate everywhere.
Every approval, escalation, and exception becomes a programmable primitive, not an untracked email chain.
Files are not just blobs. They carry structure, intent, and obligations that other engines can react to.
Roles, responsibilities, and permissions wired into actual work, not buried in some admin page no one touches.
Founding Principles
The rules I refuse to break.
No design decision is allowed if it makes life easier for the system but harder for the person using it.
Every "feature" must be backed by a reusable engine that can power five other things later.
If it doesn't survive the chaos of an actual project site or finance desk, it doesn't ship.
Timeline
How this turned from frustration into a platform.
Step 1 — RCL Reality Check
Years of bending real-world operations around rigid ERP logic made the core problem impossible to ignore.
Step 2 — Engines, Not Modules
Instead of "build HR," the goal became "build a People engine." Instead of "build DMS," it became "build a Document engine."
Step 3 — Solo, By Design
No VC deck, no roadmap theater. Just a founder, a keyboard, and a long-term contract with reality.
One Spine.
Many Surfaces.
Fyboard isn't a collection of disconnected apps. It is built on three shared engines—the backbone of the platform.
This means that if you use FyBrain to summarize a file, that same intelligence is available in your contracts, your forms, and your workflows.
"Everything is connected by default."
FyBrain
Intelligence Layer
Tagging, extraction, & summaries.
Workflow
Orchestration Layer
Approvals, routing, & SLAs.
FyDrive
Document Layer
Permissions, versions, & audit logs.
2029
Replacing SAP at Raj Corp.
We have a bold internal milestone. By 2029, we plan to replace our current SAP ERP implementation at RCL completely with Fyboard.
"If Fyboard can power RCL's contracts, procurement, finance, and projects, it proves it can scale as a true ERP alternative."
The Long Game.
We aren't building for a quick exit. We are building infrastructure. Whether you are a freelancer needing better files, or a CEO tired of ERP lock-in, Fyboard is designed to grow with you.
Fyboard is a long journey—proven inside RCL first, opening to the world step by step. But whether you're an individual looking for better daily tools or an organization ready to rethink enterprise systems, you're invited to be part of the story from day one.
EARLY ACCESS IS CURRENTLY INVITE-ONLY