FurnishiShow, do not tell
Every screenshot on this site is the running build. When something is designed but not built, we label it.
Home Company
We built this by reading one factory's spreadsheet very carefully.
Furnishi did not start from a market-size slide. It started from an operating workbook — the actual sheets a modular factory uses to run installation — and the question of why the same customer name was typed into four of them.
How it began
The four-sheet problem.
The workbook had four sheets that looked almost identical: an enquiry sheet, an order sheet, a snag sheet and a partner sheet. Almost identical, but not quite — each one had a slightly different set of columns, and the differences were not accidental. The partner sheet had no customer name. The coordinator sheet had no factory area. The snag sheet had a cost column that appeared nowhere else.
Somebody had, by hand, over years, built a field-level permission system out of copy-paste. It broke constantly — the sheets drifted, a name got pasted into the partner copy, a cost went out to a coordinator. But the intent was exactly right, and no off-the-shelf system did it.
So Furnishi was built around that intent. One order record in the database, and the four sheets became four views on it — which means they can never drift again, and the customer name is not omitted from the partner copy, it is not in the partner copy.
Every serious operational problem in this business is a permissions problem wearing a different hat. Late jobs, leaked customers, disputed payouts — all of it is somebody seeing something they should not, or not seeing something they should.
How we work
Four commitments.
Say what is missing
Our security page lists what we do not have yet. Our customer-app page lists the eight questions we still cannot answer.
The factory owns its data
Not the platform, not the partners. Export any time; full export on exit.
Small enough to answer
You will talk to someone who has read the schema, not to a tier-one queue.
Where the product is
Build status, plainly.
| Component | Status | Detail |
|---|---|---|
| Factory Manager panel | Working build | 17 screens, role switching, permission matrix live. Screenshots on this site are from it. |
| Super Admin console | Working build | Tenants, rate card, masters, billing, reports, audit, platform users. |
| Database schema | Built & verified | 66 tables, 15 enums, 116 indexes, 5 enforcement triggers. Executed against PostgreSQL 16 with business rules tested by live insert. |
| Customer mobile app | Designed | 62 screens and 24 modal states specified and designed. Eight open questions before build. |
| Partner mobile experience | Designed | Runs in the browser today; a dedicated field app is next. |
| Public API | Planned | Group plan. Webhooks first, then a read API. |
Contact
Talk to the people who built it.
No SDR, no qualification form. A working session on your orders with someone who can change the product.