Question 1

What does a project cost?

Accepted Answer

Most builds land between a focused MVP and a full platform. We quote a fixed price after a paid discovery, and that price holds unless you change the scope.

Question 2

Why do you charge for discovery?

Accepted Answer

Because it is real engineering work that produces a written scope, an architecture sketch, a risk register and a release plan. If you do not proceed with us, you keep all four.

Question 3

What happens if the scope changes?

Accepted Answer

It is quoted in the same format as the original: a description, an estimate and the effect on the release date. You approve it or you do not. Nothing is absorbed silently.

Question 4

Do you work on time and materials?

Accepted Answer

For dedicated teams and on-demand support, yes. For defined builds we prefer fixed price, because it puts the estimating risk on us where it belongs.

Question 5

Is there a minimum engagement?

Accepted Answer

Discovery is the smallest piece of work we take. Beyond that, the smallest useful build is usually four to six weeks.

Question 6

How long until we see something working?

Accepted Answer

A usable build in about six weeks on most engagements, and a demo at the end of every two-week increment before that.

Question 7

How much of our time do you need?

Accepted Answer

Roughly two hours a week from a decision-maker, plus the demo. Projects stall when nobody on the client side can decide.

Question 8

What if we need to pause?

Accepted Answer

Increments are the natural stopping point. You can pause at the end of one, and we will document where things stand.

Question 9

Do you use our tools?

Accepted Answer

Yes. Your repository, your tracker, your chat. We do not ask clients to log into a portal we own.

Question 10

Who is on the team?

Accepted Answer

A named set of engineers and a designer, all on our payroll. No subcontracting, and the same people stay through the project.

Question 11

Who owns the code?

Accepted Answer

You do, from the first commit. It sits in your repository with documentation, and there is no proprietary framework tying you to us.

Question 12

How do you choose the stack?

Accepted Answer

By what fits the problem and what you can hire for later. Usually React and TypeScript, Node or Python, Postgres, and Flutter or React Native on mobile.

Question 13

Do you take over an existing codebase?

Accepted Answer

Often. We start with an audit, tell you honestly what is worth keeping, and give you a repair plan or a rebuild plan with the reasons written down.

Question 14

How do you handle security?

Accepted Answer

Access control, encryption and audit trails are designed in from the first sprint. We can work to your security review or arrange a third-party test.

Question 15

Where is our data hosted?

Accepted Answer

In your own cloud account, in the region you choose. We do not host client production data on infrastructure we own.

Question 16

When is AI actually the right answer?

Accepted Answer

When there is volume, the task is repetitive, and a wrong answer is recoverable. If any of those is missing, we will usually recommend against it.

Question 17

How do you know a model is good enough?

Accepted Answer

A labelled evaluation set and a target metric agreed before the build, so quality is measured rather than asserted.

Question 18

What about hallucination and errors?

Accepted Answer

Retrieval grounded in your content, confidence thresholds, and a human review queue for anything below the line. A low-confidence answer does not reach a customer unchecked.

Question 19

Do you fine-tune models?

Accepted Answer

Sometimes. Retrieval solves the problem more cheaply more often, so we try that first and say so when fine-tuning is genuinely warranted.

Question 20

How is running cost controlled?

Accepted Answer

Token budgets, caching and per-feature ceilings, monitored after launch with alerts on spend as well as errors.

Question 21

What does support include?

Accepted Answer

Monitoring, bug fixes, dependency and OS upgrades, and a named engineer who knows the codebase. Retainer or on-demand hours.

Question 22

How fast do you respond?

Accepted Answer

Retainer clients get a same-business-day response and an agreed target for anything blocking production.

Question 23

Can our own team take over?

Accepted Answer

That is the intended end state. Documentation, handover sessions and a support taper are part of the plan.

Question 24

Do you keep adding features?

Accepted Answer

Yes, either as small quoted pieces or a rolling dedicated team, whichever suits the pace you need.

Question 25

What if we stop working with you?

Accepted Answer

You keep the code, the documentation and the accounts. There is nothing to unwind.

Questions, answered plainly

Pricing & contracts

What does a project cost?

Why do you charge for discovery?

What happens if the scope changes?

Do you work on time and materials?

Is there a minimum engagement?

Stop forcing generic tools to fit a custom business