Compare
The capability you already own, informally.
The spreadsheet beside the system and the approval in the group chat are software your own people built, for your own operation. This page respects why they exist, says what they cost, and shows how a first build turns them into a system without losing what was fast.
What the sheet really is
Your team already built its own software.
Look at the spreadsheet your operation opens first each morning. Nobody bought it. Someone on your team made it, for your process, in your words. When the process changed, they changed it the same day. No vendor was asked.
That is ownership, in the sense this site uses the word: you decide what is built and when, and the knowledge stays with your people. The sheet and the group chat are the one part of your software you already own. They are owned informally, and that is where the cost comes from.
Why teams work this way
It is fast, and it bends.
A spreadsheet can be started in a minute by the person who needs it. When a delivery arrives short, someone adds a remark and the work carries on. No ticket, no waiting.
A group chat is faster still. The person who must approve is already in it. A photograph of the slip, a one-word reply, and the truck moves.
These tools appear wherever formal software does not fit the work. They are the mark of a team that got the job done with what it had. Anything that replaces them has to be as quick at the moment of entry, or people will go back.
What it costs
Four things a sheet and a chat cannot give you.
- No one version. A file is copied, renamed and mailed. Two people hold two truths.
- No history. A cell shows what it holds now. A chat scrolls away, and the message that mattered is somewhere above.
- No permission. Whoever has the file can change the figure. Whoever is in the group can say yes.
- Nothing reconciles. The receipt register, the status sheet and the accounts each hold their own number, and a person has to make them agree.
There is a fifth cost, and it is the one that matters to an owner. The rules live in one person's head: which column means what, which remark means the order is short, who may say yes in the group. When that person is away, the capability is away too.
None of this hurts on a quiet day. It hurts when someone asks about last month: who agreed that rate, why that weight was changed, what happened to the rest of that order.
Documented, not imagined
How four operations ran before.
These are the states recorded during discovery, before anything was built. None of them is unusual, and each one worked well enough to run a real business.
Engineering group · spares and consumables
One spreadsheet file per quotation, renamed by hand. Proforma invoice numbers assigned by hand. Partial deliveries typed into a remarks cell as dated notes. Who was asked to buy what was agreed by voice or by message. The system the engineering group runs now.
Power producer · biomass fuel
Lab results for loose fuel went to a WhatsApp group, one message per sample. Plant teams kept stock and consumption in spreadsheets, and the daily consumption summary did not link back to individual weighbridge slips. The system the power producer runs now.
Wealth firm · wealth management
Portfolio reporting to clients happened over WhatsApp. Statements were taken in over WhatsApp and ad hoc spreadsheets, with no structured record of which family members made up a household. The system the wealth firm runs now.
Textile house · textile finishing
The factory floor ran on handwritten registers, forms and notebooks, carried to head office for data entry. The packing plan was worked out in the manager's head, against stock checked physically or from memory. The system the textile house runs now.
Jetbro's own office was no different. Leave was announced in a chat channel and logged separately in a spreadsheet, with no running balance. Jetbro has since built its own HR portal on Phlo.
Side by side
What each one gives you.
| Spreadsheet and group chat | On Phlo | |
|---|---|---|
| Starting | This afternoon. Nobody has to approve a new sheet. | Two to five weeks for a first build, beginning with a visit to watch the work. |
| A case nobody planned for | Add a column, or type a remark. The work carries on. | Mapped before the build and given its own step, so it leaves the same record as the normal case. |
| One version | One file per quotation, renamed by hand. The latest is whichever was saved last. | One record per order. A revision is a new version, and the earlier one stays. |
| History | A cell holds its current value. What it held before is gone when the file is saved. | Every change is an event with a time and a person. The original never disappears. |
| Permission | Anyone with the file can change any cell. | Each action belongs to a role. Raising a purchase order and approving it are separate permissions. |
| An approval | A message in a thread, not attached to the thing approved. | An event on the record it approves, with the approver and the time. |
| Reconciling | Done by a person, comparing sheets, when there is time. | Stock, status and pending quantity are worked out from the same events. |
| Where the rules live | In the head of whoever keeps the sheet, and in the habits of the group. | Written down as a model of your operation: entities, events, exceptions. |
How the first build uses it
The sheet is the best specification you have.
A first build on Phlo starts on your floor, and the sheet is one of the first things we ask to see. Its columns say which facts the operation needs. Its remarks say where the exceptions are. The group chat says who decides, and how quickly they are expected to.
Each of these is carried across on purpose. A column becomes a field. A dated remark becomes an event. The person who says yes in the group becomes a role with a permission. The rule only one person knew is written into a specification you sign before any code exists.
The same work, recorded
The remark in the cell becomes an event.
Take a short delivery. In a status sheet it is a dated note in a remarks column. On Phlo it is a goods receipt for three lines out of four. Nothing else is written down, because the fourth line has simply not moved.
One order, one afternoon
- 10:12PI lockedPI-0031/26-27 · the client's order number recorded
- 10:15Work allocation confirmedJobs appear for two purchase workers
- 11:40PO createdOne vendor · waits in Pending Approval4 lines
- 12:05PO approvedReleased by the purchase approver
- 16:20GRN createdReceived at the warehouse. One line short3 of 4 lines
- 17:02Sales invoice createdThose lines move to Delivered. The fourth stays at PO Raised3 lines
What was fast stays fast. In that system two reports are laid out like the spreadsheets they replaced, and reports export to a spreadsheet. The phone call to the client still happens. The decision it produced is now on the order.
What you own afterwards
The same capability, owned properly.
The first build is not a pilot. It is where your operation gets described: its entities, its events, its exceptions. That description is written down, so it no longer depends on who is at their desk.
What made the sheet yours does not change. What gets built, and when, is still your decision. After the first build the framework becomes available to you, so your own engineers can build the next system on it, or we carry on. The second system starts from roles, approvals and a history that already exist.
When a spreadsheet is right
Keep the sheet when the sheet is enough.
- The process is new. If the steps change every week, a sheet is the right place to find out what they are.
- It is analysis, not record. Modelling a price or planning a budget is what a spreadsheet is for.
- Nothing rests on it. If no money, stock or approval depends on the figure, its history does not matter.
Move it into a system when the sheet has become the record: when several people write to it, when money or stock follows from it, and when somebody will one day ask who changed it.
Owned against bought or rentedWhy building no longer takes a year
Get started
Show us the sheet everyone opens first.
Tell us which register or group chat your operation would stop without. That is usually the capability to own first.
coffee@jetbro.inWhatsApp +91 90999 62227