Question 1

Why pay for Services if I can just buy Apollo direct?

Accepted Answer

Apollo direct sells you the engine. Services sells you the engagement around the engine. The milestone fee on Path 1A isn't the cost of the code Apollo writes — it's the cost of brief scoping, milestone planning, project management, delivery accountability (klair absorbs milestone slippage), engineering review of every change before you see it, and time-to-first-ship from a one-paragraph brief. If you have an engineering team with a backlog and a CI and time to drive the work, Apollo direct is what you want. If you have a project and a deadline and you don't want to grow an engineering team to ship it, Services. The choice is real both ways.

Question 2

How do payments work?

Accepted Answer

Per signed milestone, not per hour. Each milestone has a deliverable and a sign-off. You pay when the milestone is signed. No surprise invoices. No claw-back. If we can't deliver a milestone at the price we named, that's our problem to absorb.

Question 3

Can we pause between milestones?

Accepted Answer

Yes. Stopping between milestones costs nothing. The architecture is built around it: each milestone is bounded, signable, and self-contained. You can pause for a quarter, come back, and we resume the plan. The only commitment is per-milestone — never the whole project up-front.

Question 4

How much do I need to know before I can get a plan?

Accepted Answer

One paragraph. The intake drafter (Hermes) asks a few clarifying questions, then returns a structured proposal with scope, milestones, and a number. No deck, no discovery week. Inside klair, our engineers review the brief and challenge it before the milestone plan is drafted.

Question 5

What happens when scope changes mid-build?

Accepted Answer

Change-orders are first-class. Each one has its own price and duration delta, approved explicitly. No silent expansion. The original milestone plan stays the contract; change-orders sit alongside it with their own sign-off.

Question 6

What happens at handover?

Accepted Answer

M4 ends with deploy + docs + team hand-off. You receive: the production deploy, repo and credentials, a runbook for operating the system without us, and any architecture docs we drafted along the way. From there, two paths: take the runbook and self-host (Path 1A), or opt into Moon and we keep operating it (Path 1B). The Moon decision happens at handover, not at intake.

Question 7

Who owns the code and the IP?

Accepted Answer

You do. Code lives in your repo from day one and stays there at exit. Handover includes repos, credentials, and a runbook. No vendor lock-in. If we stop running the hosted side, you keep the code and the runbook.

Question 8

Who actually writes the code?

Accepted Answer

klair's internal engineering team. We deliver end-to-end, with Apollo as our accelerator. Nothing is subcontracted. Every change klair's engineers review before you see it — that review is part of what the milestone fee covers.

We build software for you.

The build cadence, in ninety seconds.

Four milestones. One signable plan.

The price isn't the cost of the code. It's the cost of the engagement around the code.

Our products are our proof.

Hermes

Apollo

Moon

Stay hosted at handover.

Services, answered.

One paragraph in. A milestone plan out.