The questions owners ask on the first call.
If yours isn't here, ask it on the call. We'd rather answer it than have you guess.
How does an engagement usually start?
With a thirty-minute call, then almost always with discovery. The problem an owner describes first is rarely the one costing the most, and we won't quote a build against a problem we haven't watched happen.
Am I committed to the build after discovery?
No. Discovery is scoped and priced on its own, and what you get back — the findings and the roadmap — is yours to take to anyone.
How long does a build take?
A build phase runs four to five weeks from design sign-off: one week of design sessions and architecture, three weeks of module build with reviews along the way, then training and handover. Larger scopes are split into phases rather than stretched.
How is it priced?
Fixed price per phase, split into milestone payments — typically at signing, at design sign-off, and at delivery. Ongoing advisory is a flat monthly fee. Scope changes need a written change order first, so nothing arrives as a surprise.
Who owns the code?
You do, on final payment. We retain no license to it. Where it makes sense, the application runs on your own infrastructure under your security team's monitoring, not ours.
What happens if we stop working together?
Everything keeps running. Rates and rules change in an admin screen rather than in code, your operators are trained and have a runbook, and the handover documents explain how it fits together.
Will you have access to our bank accounts?
No. On payment-related builds we don't take banking portal access at any stage. Money moves through the accounting platform you already use, triggered by a system your own people approve in.
Will our name appear on your website?
Not unless you ask for it. Case studies are published by industry and company size, with client names, internal names, and figures withheld by default.
How much of my time does this take?
During design week, expect two sessions of about sixty to ninety minutes. During the build, short check-ins of thirty minutes or less. The heaviest ask is honesty about how the process actually runs.
We already have developers. Where do you fit?
Usually above them. We own the technical decisions and direction, and coordinate with your team on the pieces that belong to them. We'll say clearly which work is ours.
Do you use AI in the work you deliver?
Where the task is repetitive, rule-bound, and reviewed by a person before it counts — preparing forms, reading invoices, drafting copy in a documented voice. A person approves the output. Nothing files, sends, or pays on its own.
Do you work on site?
For discovery and training, when it's useful to be in the room. The rest is remote. We're based in Florida and work with clients elsewhere.