Most business tools open with a form. Name, industry, goals, a dropdown for company size, a checkbox for what you already have in place. By the time you finish, you have told the tool everything except the one thing that matters: what your business actually does.
Balise starts differently. There is a text box, and it asks for one sentence, the kind you would say out loud if a friend asked what you do. A dog groomer who wants appointments booked automatically. A coach building a high-ticket offer. A mobile detailing brand with a phone that answers itself. That sentence is the whole interview.
What happens after you hit send
Your sentence goes to a planner, and the planner writes a roadmap in plain English, not a spec sheet full of jargon. It reads back what it understood about your business, and it lays out what it intends to build: a brand direction, a site structure, the pages that make sense for what you do, and which add-ons would actually help versus which ones would just add noise.
Nothing builds yet. The plan comes back to you first, and you approve it, edit it, or send it back with a correction before a single page, domain, or phone number gets touched.
Why the approval step is not a formality
It would be faster to skip the approval step and just build something. We do not, on purpose. AI plans are good, not psychic. The planner might read "mobile detailing" and assume you serve neighborhoods when you actually only work fleet contracts. It might assume you want online booking when you would rather every lead call in first. Those are the kinds of details a one-sentence prompt cannot always carry, and they are exactly the kind of thing a human catches in ten seconds of reading a plan.
The plan comes back to you first, and you approve it, edit it, or send it back before a single page gets built.
So the plan is not a progress bar you wait through. It is the one moment where the whole build gets steered by you before any of it becomes real, and it is also the moment that makes the rest of the process fast, because everything after approval runs without you having to referee each individual decision.
What gets built once you approve
Once you approve the plan, a team of AI agents goes to work on it, and each one owns a piece: a brand direction, a real site built from your description rather than a generic template, a domain if you want one attached, and a booking calendar if your business takes appointments. Each agent reports done as its piece lands, so you are watching a build happen rather than staring at a spinner.
If your plan calls for it, an AI front desk goes live at the same time, answering calls and website chat from day one and booking what it can straight onto your calendar. It does not wait for you to configure it later. It is part of the same build, on the same login, running on the same pool of credits as everything else.
The team keeps working after launch
Launch is not the finish line. The same roadmap that got your business built keeps scoring how you show up on Google and the AI answer engines, and it keeps a queue of the next fix worth making, so the plan you approved on day one keeps paying off well past it.
None of this requires you to know what an agent, a credit pool, or a booking calendar are before you start. It requires one sentence, and a couple of minutes to read a plan and say yes. The rest is the part we built the roadmap to handle.