The Fyboard story
2024 → March 2028Forged in concrete. Refined by code.
Fyboard began on construction work in India — among drawings, vendors and approvals that couldn't wait for software to catch up. This is how it got from there to here, and the test it has set itself next.
00 · Records / FYB-0001
Fyboard's own record — this page is its history.
Every chapter below is an entry on it: what happened, when, and what it left behind. The record is still open — the last entry is yours.
2024 → March 2028
- 2024Began on site
- NowFirst tools public
- 2028The test
01 · Noted · Before 2024
The work didn't fit the software.
01 · Fourteen places
One drawing revision, in fourteen places.
On construction work, a drawing revision took six clicks to log — and then lived on in email, chat, a register, a photo, a printout. Every copy disagreed, and the site built to the old one.
- Fwd: GA-114 — Rev C attached
- Six clicks to log a revision
02 · Old org chart
Approvals on an org chart years out of date.
Approvals followed who used to sign, not who signs now. A drawing change sat fourteen days waiting on one approver.
- Change drawing · Waiting 14 days
- RE: RE: RE: which drawing is current?
03 · The spreadsheet
The vendor list, emailed around.
The vendor list lived in a spreadsheet, emailed around the office — and every inbox held a slightly different one.
- Vendors_FINAL_v7 (2).xlsx
- “v7 (2) i think. or the one Asha sent”
04 · One record
What if it were one record?
The big systems told people how to work. The newer apps were lovely on their own and shared nothing. The middle was missing: something that holds one record, and bends to the work.
- Fourteen places → one record
02 · Created · 2024
So we started where the work is.
Fyboard began in 2024 on construction work in India — highways and power lines, where a drawing, a vendor's papers and an approval all have to line up before anything gets built.
No imaginary problems. It was shaped by the people doing that work, one ordinary day at a time, and built by an operator rather than a consultant: someone who ran the work before writing the software for it.
“Software should adapt to people, not force people to adapt to software.”
- Shaped on site
- Made in India
- Foundations first
The work it was built for
A day on Ring Road · Package 3
Six ordinary moments — a drawing revised, a vendor onboarded, a variation approved, steel received, a clause flagged, a question asked — each struck out of its old channel and landing as a record.
03 · Decided · Day one
Engines, not apps.
The quick way was a pile of apps — one for approvals, one for files, one for search — each holding its own copy of the truth.
We took the slow way. Every capability became an engine that every record shares, so an improvement lands everywhere at once. Slow on features, fast on foundations.
Human first
Nothing that makes the system's life easier and the person's harder.
Engines over features
Every feature is backed by something reusable.
Reality over decks
If it wouldn't survive a site or a finance desk, it doesn't ship.
04 · Built · 2024 → now
Then we built it, in that order.
01 · Records
Records first
We mapped the work as records — fields, types and relations — before drawing a single screen.
02 · Engines
Engines under every record
History, access, files and rules arrived once, and every record got them.
03 · Modules
Modules on top
Contracts, drawings, approvals, people — each module a view onto the same records. Nothing is copied.
04 · Intelligence
Intelligence that cites
FyBrain answers from your workspace, shows its sources, and checks every citation against the record it came from.
05 · Real work
Real work on it
Internal beta, by invitation: seven modules in the hands of the people they were built for, with real work on them — one more in development and three in the pipeline.
05 · Opened · 2026
Then we opened the doors — a few at a time.
In 2026 the first six tools opened to everyone — FyPDFs, FyDark, FyShot, FyInvoice, FyPayrun and FySign. Small and self-contained: useful on day one, and the craft tested in public before anything bigger is.
The modules follow one at a time. Each opens when it's stable, not when the calendar says so — and until then, its status says exactly where it stands.
- Open to everyone
- Free to start
- Modules next, one by one
Open the first tools to everyone
- Owner
- Fybyte
- Opened
- 2026
- Who can use it
- Everyone
- Price
- Free to start
- FyPDFsMerge, split, compress & convert PDFsPublic
- FyDarkImage studio for edit, batch & exportPublic
- FyShotAnnotate, redact, mock up & exportPublic
- FyInvoiceCreate invoices & export PDF filesPublic
- FyPayrunRun payroll, generate payslips, file compliancePublic
- FySignSignature fields, signing, the signed PDFPublic
Next through the doors
Seven modules on internal beta · one in development · three in the pipeline
06 · Due · March 2028
The test we set ourselves.
By March 2028, an entire infrastructure company runs on Fyboard end to end — contracts, drawings, purchasing, projects, people, payroll and finance — with its old ERP switched off.
Not alongside it: instead of it. If we make it, that's evidence, not opinion.
If we miss it, we will say so plainly, with the post-mortem published.
- Public, and dated
- One milestone
- Post-mortem if we miss
Run a whole company on Fyboard
- Owner
- Fybyte
- Due
- March 2028
- Visibility
- Public
- If missed
- Post-mortem, published
- ContractsAlphaCorePublic
- Drawings & signed PDFsFyDriveInternal beta
- Approvals, everywhereAutomationInternal beta
- Vendor registration & site formsDataBoardIn development
- Memos & SOPsFyDocInternal beta
- People, payroll & rolesPeopleInternal beta
- Purchasing & stockMaterialsIn pipeline
- Projects & cost controlProject SystemIn pipeline
- FinanceFinanceIn pipeline
Switches off by March 2028
NextYou
The next entryis yours.
Everything on this page runs on records like these. Fyboard isn't built for a quick exit — it's infrastructure, opened step by step: the tools first, the modules one by one. Start with one record; it'll still be there when you're a company.
Forged in concrete · Refined by code