For teams · product teams & departments
One record.Everyone on it.
Requests, approvals, projects and decisions — each one a record the whole team works on, instead of a thread everyone has to chase.
Six kinds of thing · one team
- Request
- Approval
- Project
- Vendor
- Doc
- Decision
01 — Sound familiar?
The meeting that should have been a record.
Half the week goes on asking where things are: who has it, what it's waiting on, whether anyone approved it. A record answers all of that without a meeting.
02 — Built in
Built in, not bolted on.
Files, docs, approvals, forms, reports and a calendar — all reading the same records, so the team never works from copies.
Team files that follow the work.
Files live on the request, project or vendor they're about — versioned, with access that comes from the record, not from whoever forwarded them.
03 — Everything is a record
Everything your team runs is a record.
Requests, approvals, projects, vendors, docs and decisions — six kinds of thing, one way of working. Each keeps its history, its files, who can see it, and answers you can ask for.
Design tool licences
8 seats · for the design team
- Requested by
- Aisha Khan
- Amount
- $2,400 a year
- Approvers
- Design lead · Finance
- Needed by
- Friday
Every record comes with
- History
- Access
- Files
- Rules
- Ask
Waiting on Finance
04 — An approval, start to finish
An approval without the chase.
01 / 05
Asked for, once.
Leo fills in the purchase form — eight laptops, the budget line, the quote. It arrives as a request, not an email.
02 / 05
Routed by the rules.
Over $1,000 goes to Finance; over $10,000, to the Head of Operations as well. Nobody had to work out who to ask.
03 / 05
Sent back, with a reason.
Finance asks to split it over two quarters — a comment is required, so the reason stays on the request. Leo halves it and resubmits; the second approval falls away.
04 / 05
Nobody chased.
Finance's approver is away. After two days without a reply, the request moves to the backup on its own.
05 / 05
Approved, every step kept.
Sofia approves. Who asked, what changed, who routed it and who said yes — all on the request, nothing to rebuild from a thread.
05 — Ask
Ask what the team already knows.
FyBrain answers from what's in the workspace — who decided, what's waiting, what was agreed — and shows where each answer came from.
AskFyBrainAnswer
“What's waiting on Finance this week?”
Three requests — the design licences ($2,400), the event deposit and the laptop refresh. The licences have waited two days.
- REQ-0214
RequestDataBoardREQ-0214
Design tool licences
8 seats · for the design team
VendorMaterialsVEN-0042
Pixelworks Ltd
Design services · since 2023
DecisionDataBoardDEC-0021
Quarterly vendor reviews
Decided at the ops review
06 — A week
One week, no status meeting.
What a working week looks like when every piece of work knows where it is.
Mon 09:00
Requests, not an inbox
The week's requests are already records, each with an owner and a date.
Tue 11:30
Decided, once
The vendor call ends with a decision on the record — not in someone's notes.
Wed 14:00
Sent back, with a reason
Finance asks for the team plan; the request comes back with the comment on it.
Thu 10:00
Nobody chased
The approver was away, so after two days the request moved to the backup.
Fri 16:00
The week, in one view
What's done, what's waiting and on whom — nobody had to ask.
07 — Access
Access that matches how you're organised.
Roles for teams, rules for records, and one place to see who can open what — so sharing never means forwarding.
08 — Moving in
Bring the trackers with you.
Spreadsheets, shared drives and meeting notes — import them once and they arrive as records, matched to the right fields. Anything that needs a look is flagged, not guessed.
09 — Trust
The team's work, in the right hands.
Plain facts about where your records live and who can reach them — no badges we haven't earned.
Access by role, not by forwarding
Give a team, a role or one person the records they need — and take it back in one place.
Every approval on the record
Who approved what, when and with which comment stays on the record it decided.
Where it lives
Hosted in India (AWS Mumbai) for launch. Other regions may follow, by plan or agreement.
Locked in transit and at rest
TLS on the way in and out; storage encrypted at rest where it's configured.
Who can see what
Role-based access on every record — the permissions engine checks each request.
What changed, and who
Changes are logged with the person, the time and what was there before.
AI, only when you use it
AI features call outside model providers only when you use them — and every answer shows its sources.
Yours to take
Export and deletion on request during launch; after cancelling, exports stay available for 30 days where technically possible.
10 — Grows with you
From one team to the whole company.
Add a department, then another — the same records, the same rules. There's nothing to migrate when you grow.
- See the pageFor youOne person
- Clients & contracts
- Invoices & receipts
- Files & notes
- You're hereFor teamsA team or department
- People & roles
- Approvals
- Shared views
- See the pageFor startupsA growing company
- Hiring & payroll
- Finance & vendors
- A data room
- See the pageFor enterprisesA group of companies
- Access profiles
- Staged rollout
- Audit at scale
11 — Pricing
Pricing, plainly.
No bundle to decode. Each module your team would use, where it stands today and where its prices live — plus FyTools, which your team can use right now.
The modules you'd use
- AutomationApprovals and routingInternal betaPricing
- DataBoardRequests, forms and viewsIn developmentPricing at launch
- FyDocSpecs and decisionsInternal betaPricing
- FyDriveTeam filesInternal betaPricing
- FyBrainAsk across the team's recordsInternal betaPricing
- Project SystemProjects and tasksIn pipelinePricing at launch
Available today
FyTools
Standalone tools you can use now — for invoices, PDFs, images, screenshots and payroll.
- Free ForeverFree forever
- Cloud ProFrom $4 per tool / month
- TeamFrom $19 per seat / month
12 — Questions
Fair questions, straight answers.
What teams ask before they move their work in.
Do we have to move everything at once?
No. Start with one process your team runs every week — requests, say — and bring the rest in when it's worth it. What you add later links to what's already there.
Can people outside the team take part?
Yes. Invite them to just the records they need; they see what you share and nothing else.
Who approves what?
You decide. Approvals route by role or by a rule on the record — an amount, a department, a vendor — with a backup when someone's away, and a required comment when something's sent back.
Can we use it today?
Fyboard is in internal beta, and each module opens as it reaches public launch — you can see where each one stands on this page. FyTools are live now.
What does it cost?
Each module is priced on its own, and the ones still in development or in the pipeline show their price at launch. FyTools have a Team plan from $19 per seat a month, with a 3-seat minimum.
Does it work with our email?
Gmail and Outlook are the first connectors in FyIntegrations, which is on internal beta. Until it opens to everyone, forms and imports bring the work in.
Where is our data, and who can see it?
Hosted in India (AWS Mumbai) for launch, encrypted in transit, and at rest where configured. Access is by role, down to the record.
Does AI read our records?
Only when someone uses an AI feature. FyBrain answers from your records and shows where each answer came from; outside model providers process data only for the features you choose to use.
Can we leave with our data?
Yes. During launch, exports and deletion are handled on request; after cancelling, exports stay available for 30 days where technically possible.
Your team's workspace
Stop chasing. Start deciding.
Start with one process your team runs every week. The rest can follow when it's worth it.
Requests & approvals
One form in, routed by rules, with a backup when someone's away.
- Requests
- Approvals
Specs & decisions
Docs the team writes together, and decisions that stay decided.
- Docs
- Decisions
Vendors & renewals
Every vendor with its files, its contract and the date it renews.
- Vendors
- Contracts
Tom Becker Approved — the team plan works for us. @Aisha