FAQ
Questions, answered plainly.
What owners, operations heads and CIOs ask before they talk to us, starting with what they own at the end. Where an answer depends on your engagement, this page says so instead of guessing.
Owning it
What is yours at the end, and who builds what comes next.
What do we own at the end of the first build?
Three things. A working system for one part of your operation, on its own instance and database. A record of everything that has happened in it, which cannot be quietly rewritten. And the model of your operation, written down: its entities, its events and its exceptions.
By owning we mean that you decide what is built and when, the knowledge stays with you, and you can build on the foundation yourself. Licence and source-code terms are settled in the first conversation, scoped to the engagement. What is owned, in full.
Can our own team build on what the first system leaves?
That is the purpose of the second stage. After the first build, the framework becomes available to you, and your own engineers and product people can build the next system on it.
They do not start from nothing. Events, roles and permissions, approval chains and reporting already exist, and so does the written description of how your operation runs. Phlo Framework.
What happens after the first system?
The first build is not a pilot. It is where your operation gets described, and that description is what every system after it is built from. Who builds those is up to you: your own engineers on the framework, or us.
Either way the foundation carries forward. A second system reuses the roles, the approval chains, the reporting and the recorded history of the first. The two stages, in order.
Do we have to keep using Jetbro?
Not for building what comes next. The offer has two stages. In the first, Phlo Enterprise Systems, we build the first system with you. In the second, Phlo Framework, the framework becomes available to you: your own engineers build the next system on it, or we carry on building for you. Both stay open.
The knowledge is written down in the model of your operation, so it does not leave when an engagement ends. The terms are settled in the first conversation, scoped to the engagement.
What are the terms of the framework stage?
They are settled in the first conversation and scoped to the engagement. This site does not publish licence terms or pricing for that stage, because they depend on what is built first and on who will build next.
What is fixed is the principle: after the first build the framework is available to you to build on. Ask us about your case.
The first build
How the work runs, from the first conversation to go-live.
How long does a first build take?
Two to five weeks, start to live. Every first build runs through the same six steps: discovery on site, process mapping, scoping and sign-off, build, review and launch. Your team is trained at launch, and hosting and support start on day one.
It is fast because most of it is already written in the framework. How the first build runs, step by step.
How is that faster than a traditional custom build?
A traditional build writes its foundations again for each project: sign-in, roles, approvals, the audit log, reporting. On Phlo those already exist and already run in production, and AI writes the remaining code to an agreed specification.
We state the result as at least 3x faster than top tier IT services firms. Where the time goes in each kind of build.
What is the first conversation like?
It is about your operation, not a demo. Every system is scoped and built with you, so there is no standard product to walk through.
You tell us how the operation runs today and which capability you want to own first. We come back with the processes, the scope and the timeline for a first build.
Do we see what we are getting before it is built?
Yes. The specification is agreed before any code is written. It defines every screen, every action and every data field, and you review and sign it off.
The system is then built to that specification, and your team tests it against the same document before anything goes live.
What do you need from our team?
Access to the operation and to the people who run it. We visit your facility and watch the work happen. Your team reviews the process map and the specification, tests the system in the review step, and is trained on it at launch.
What does the AI do, and what do people do?
AI writes the code, inside guard rails built into the framework. People do the rest: they visit the site, understand the business and its exceptions, map the processes, design the system and take every product decision.
The time AI saves in the build is spent on site with the people who run the process. How people and AI share the work.
The system
What is built, and how it behaves once people use it.
Is Phlo a product we configure, or custom software?
Custom software, built on a framework. Phlo is the framework Jetbro built for enterprise operational software: the event log, roles and permissions, approval chains and reporting are already written and running in production.
Your system is designed for your operation and built on those foundations. What Phlo is, in full.
Does it replace our ERP or accounting system?
Usually not. Most Phlo systems sit beside the ERP or accounting system. They cover the part of the operation that those products do not: how the work actually runs on your floor.
The ledger, payroll and statutory reporting are the same for every business, and packaged software is the right place for them. Owned against bought or rented.
Our process has exceptions that no software handles. What happens to those?
They are designed in. Discovery and process mapping exist to find them: every workflow, handoff and role, and every exception your team works around today. Each one is written into the specification and built as part of the system.
They also become part of the written model of your operation, so the next system starts from them.
Who can see and do what?
Roles and permissions are tied to actions. A role is allowed to take specific actions, and every action taken is recorded as an event. Raising a document and approving it can be separate permissions held by different people.
Can a record be edited or deleted after the fact?
Nothing is overwritten. Most software records what is. Phlo records what happened. A correction is a new event on top of the old one, and both remain: what the record said before, who changed it, and when.
Does it work on phones?
Yes. Systems built on Phlo work on phones and in desktop browsers.
Data and hosting
Where the system runs and how it meets your other software.
Where does our system run? Is it shared with other clients?
Each client has its own instance and its own database, on a server we manage or inside your own infrastructure. Your data is not mixed with that of another client. Hosting starts on the day the system goes live.
Which of the two applies to you is settled in the first conversation, scoped to the engagement.
How does data reach Tally?
By file export. Where a system has been built to feed Tally, it produces an export file for Tally. Phlo sits beside the accounting system and does not replace it.
Cost
How a first build is priced, and what comes after it.
What does it cost?
Pricing is not published, because no two systems are the same. Each first build is scoped after the first conversation. Once we understand the operation, we come back with the processes, the scope and the timeline.
Does a second system cost as much as the first?
No. The foundation carries forward: events, roles and permissions, approval chains and reporting already exist, and new processes sit on the history you already have, without a migration. That is why the second system costs a fraction of the first.
We do not publish a figure. The scope of a second system, like the first, is settled in conversation.
Get started
A question that is not here?
Ask us. Tell us how your operation runs today and which capability you want to own first. We come back with the processes, the scope and the timeline for a first build.
coffee@jetbro.inWhatsApp +91 90999 62227