The Fyboard Manifesto
Software that respects how you work.
Most software asks people to change how they work to fit it. We watched what that costs on construction sites, and every belief below began as one of those moments. The tool should bend, not the person. These are the beliefs we build by, and the lines we won't cross.
00 · What we believe
Signed in public, so you can hold us to them.
We build for the people who run the work — the ones who sign the contracts, chase the approvals and close the books. These are the beliefs we build by, signed in public, so you can hold us to them.
- 01Your data stays yours.
- 02Workflows that forgive.
- 03Intelligence that shows its sources.
- 04If it isn't effortless, it doesn't ship.
- 05One engine, every module.
- 06Records before screens.
- 07No surprises.
01 · Seven beliefs
What we build by — each learned on site.
01 · Your data
Your data stays yours.
Your workspace is stored in India, every file records where it's kept, and what you put in comes back out in formats other software reads — documents, tables, reports, files with their versions.
- Learned on site: Vendors_FINAL_v7 (2).xlsx — the vendor list, in whichever inbox it last landed.
- Stored in India · Standard formats · Files keep versions
02 · Forgive
Workflows that forgive.
When a step fails, Fyboard retries it on its own. If it still can't go on, the run follows the failure plan you chose — stop, carry on, take an error path or undo what it did — and the run keeps the record of what happened.
- Learned on site: A drawing change that sat fourteen days waiting on one approver.
- Retries on its own · Your failure plan · Every run on record
03 · Sources
Intelligence that shows its sources.
FyBrain answers from your workspace, cites the records it read, and checks its citations against them. It never reaches beyond your workspace, and it checks you can open the document or project you're asking about.
- Learned on site: “What changed today?” — answered by five phone calls.
- Cited records · Citations checked · Inside your workspace
04 · Effortless
If it isn't effortless, it doesn't ship.
No admin panels that need a manual. Edits save themselves, mistakes undo, and in a shared document you can see who else is there.
- Learned on site: A drawing revision that took six clicks to log.
- Saves itself · Undo · See who's in a doc
05 · One engine
One engine, every module.
Modules stand on shared engines, so one improvement — to tables, files or access — lands in every module that uses it, at once.
- Learned on site: One drawing in fourteen places, and every copy disagreed.
- Shared engines · Lands everywhere · One record
06 · Records first
Records before screens.
We define the record — its fields, types and relations — before we draw a single screen. The interface is the last thing we build.
- Learned on site: Rev C in an inbox while the site built to Rev B.
- Typed fields · Relations · Screens last
07 · No surprises
No surprises.
Rules are labelled as rules, AI as AI, beta as beta. What's live is live — and what isn't, we say so.
- Learned on site: Tools that looked finished in the demo and weren't on site.
- AI, labelled · Rules, labelled · Beta, labelled
02 · Kept in the product
Every belief, kept by a screen.
Each belief, as it looks in Fyboard — illustrative screens built from the product's own parts, showing what it does today and nothing it doesn't.
01 · Your data stays yours.
02 · Workflows that forgive.
03 · Intelligence that shows its sources.
04 · If it isn't effortless, it doesn't ship.
05 · One engine, every module.
06 · Records before screens.
07 · No surprises.
03 · Lines we won't cross
Written as clauses, so they can be held to.
Each of these would make money somewhere. We refuse them on purpose — and the list is short, because breaking one would break the rest.
§1
No features built for pitch decks.
If it doesn't hold up in real work, it doesn't ship.
§2
No AI you can't see or switch off.
We name the model — Google's Gemini, by default — and your organisation can turn AI off feature by feature, or keep it on Fyboard's own local model.
§3
No training models on your records.
Fyboard doesn't train models on customer data. What it remembers about your work stays in your workspace.
§4
No price you have to ask for to get started.
Every plan you can buy yourself has its price published. Only custom enterprise agreements are quoted.
§5
No lock-in by format.
Documents, tables and reports export to formats other software opens. A one-click export of the whole workspace isn't built yet — and we say so here.
§6
No retiring a feature without a way out.
If something goes away, the tools to move come first.
§7
No calling search “AI”.
Rules-based features are labelled as rules.
§8
No silent changes.
What changes is written up in the public changelog.
Fyboard · Fybyte
If we break one, call us out.
Seven beliefs · one signature
Build better.
Six tools are open to everyone. The modules follow one by one — each proving itself with real work before it scales.