Fyboard
One record for everything your company runs on.
Contracts, people, files, money, materials and projects — on one platform, where every module shares the same engines and the same idea of a record.
→to begin·Gfor every slide
01 · The problem
Every team keeps its own truth.
Contracts live in one tool, people in another, files in a third, money in an ERP. None of them agree, so people copy between them — and the copying becomes the job.
- 01Re-keyedThe same vendor, employee or project typed into five systems, five slightly different ways.
- 02Unanswerable"Who approved this, and against which contract?" takes a meeting, not a click.
- 03UnauditedHistory lives in whichever tool was used last, so audits stitch it back together by hand.
02 · The idea
One shape: the record.
We define the record — its fields, types, relations, history and who may see it — before we draw a screen. Modules write records; shared engines act on them.
A record
- 01Fields and relations
- A contract knows its counterparty; a purchase order knows its vendor; a payslip knows its employee.
- 02History
- Who changed what, when, and the change itself.
- 03Access
- Roles and scopes resolved on every request, down to the rows a person may see.
03 · Engines
Twelve engines, under every module.
An improvement to tables, files, access or search lands in every module that uses it, at once.
Governance · E01
Permissions
Four-tier organisation RBAC with multi-axis resolution on every request, plus dimensional row scoping and time-bounded grants.
Governance2
Backend5
Surface5
Point at an engine — or tab to it — to read its job
04 · Modules
Twelve modules, one board.
Seven on internal beta, one in development and three in the pipeline — each labelled for what it is.
- 01AlphaCoreLiveContract lifecycle — numbered records, phases, obligations, renewals, eSign and login-less guest review.
- 02FyDriveInternal betaCloud storage — drives, versions, resumable uploads, watermarked shares and role-based access.
- 03FyBrainInternal betaAsk with cited answers, memory and knowledge sources — over OCR, embeddings and semantic search.
- 04AutomationInternal betaWorkflow builder — approvals, escalations, a dry-run simulator and every run on record.
- 05DataBoardIn developmentForms, boards and reports — with payments inside forms and connectors for webhooks, Sheets and Postgres.
- 06FyDocInternal betaDocuments — suggestion mode, version history, letterhead page setup, eSign, export and web publishing.
- 07PeopleInternal betaHRMS — payroll and payslips, leave, attendance and shifts, onboarding to exit, and the org spine the rest reads from.
- 08MaterialsIn pipelineItem master and vendors, requisitions to purchase orders and goods receipts, warehouses, stock and valuation.
- 09FinanceIn pipelineGeneral ledger, payables and receivables, payment runs, banking, fixed assets, budgets and financial reports.
- 10Project SystemIn pipelineProjects and portfolios — WBS, schedules, BOQ, resources, stage gates and cost control.
- 11FyIntegrationsInternal betaConnected accounts — Gmail, Google Calendar, Google Drive and Outlook — scoped to the records they belong to.
- 12FyScheduleInternal betaOne scheduler for every module: briefs, snapshots, reminders, rules, reports and workflows on a cadence.
05 · Intelligence and automation
AI that cites, workflows that forgive.
- 01Answers with sourcesFyBrain answers from your workspace, cites the records it read and checks its citations against them. It never reaches beyond your workspace.
- 02Runs you can trustWhen a step fails it retries; if it still can't go on, the run follows the failure plan you chose — and keeps the record of what happened.
- 03LabelledRules are labelled as rules, AI as AI, beta as beta.
Either side can exit on ninety days' notice [S1]and the landlord has asked to extend by two years [S2]
- S1lease-pune-2024.pdf · p.3“either party may terminate on ninety days' written notice”
- S2Renewal email · Asha Kulkarni · 12 Jun“we'd like to extend for two more years”
site-plan.pdf · not cited in this answer
06 · Proof
Built inside real operations.
Fyboard was built inside an Indian EPC company with ₹1,300 crore+ in FY25-26 revenue — among drawings, vendors and approvals that couldn't wait for software to catch up.
- Parent group, FY25-26 revenue
- ₹1,300cr+₹1,300cr+
- Database tables, mapped
- ~1,300~1,300
- API routes
- ~4,000~4,000
- Permission functions in the database
- 1818
Platform figures counted from the code on 2 October 2026.
07 · In public
March 2028, on the record.
The parent group replaces its SAP stack with Fyboard end to end — contracts, drawings, procurement, finance, audits.
If we miss it, we will say so plainly, with the post-mortem published.
On the recordDue · March 2028
March 2028
08 · Open today
Start with what's already live.
Six tools are free in your browser — FyPDFs, FyDark, FyShot, FyInvoice, FyPayrun and FySign. ScribleSketch is open as a service.
- ToolsLivePDFs, images, screenshots, invoices, payroll and signing — free, most of it with no sign-in.
- ScribleSketchOpenNotes in, notebooks and decks out — on a Free plan.
09 · How we build
Lines we won't cross.
- 01Your data stays yoursYour 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.
- 02Effortless or it doesn't shipEdits save themselves, mistakes undo, and in a shared document you can see who else is there.
- 03No surprisesWhat's live is live — and what isn't, we say so.
10 · Working together
Tell us what you run.
Whether you run contracts, people, procurement or projects, start with what's open today, follow the modules on the public roadmap, and talk to us about the rest.