What happens after I buy a credit?

After you pay, you're signed in with one credit, good for one Build Specification for one application. When you're ready, you start your project, set its scope, invite the people who know the work, settle the gaps and disagreements their answers turn up, sign off, and hand the finished specification to whoever will build it.

Here is how each step works.

How do I buy a credit?

On the Start a project page you give your work email, a few sentences about what you want built, and optionally your company. Payment is on Stripe's own checkout page, where you also accept the Terms of Service and the Refund Policy. Mochlion doesn't see your card or bank details.

When the payment is confirmed, your login and your credit are set up, and a sign-in link and code are emailed to you. If you pay by bank transfer, that happens when the transfer clears.

Why isn't my project started automatically?

Because starting it is your decision. An unused credit can be refunded if you ask within 90 days of purchase; once a project has been started with it, it can't. So you get a short Getting started page first, then you start the project with one click when you're ready. Unused credits don't expire. The Refund Policy has the details.

What do I do first?

Describe the problem and the outcome you want, and approve the project's scope. Approving the scope fixes which application this credit covers. You can also add documents you already have and, if there's an existing database, import its structure (not the data in it).

Who answers the questions?

The people who know the work. You invite them from inside your project: operations, finance, the front line, IT, whoever holds a piece of it. Invite as many experts as the project needs; they are all included.

Each expert answers only their own questions, on their own time, from a phone or a computer, typed or spoken. If you have an AI agent that knows your systems, you can add it as an expert too.

What happens to the answers?

Mochlion works out what to ask the right people, compares their answers, and surfaces the gaps and disagreements. A conflict goes to a person who can decide it, who sees each side and records the decision and the reason. Assumptions stay assumptions until a person confirms or rejects them.

Only people decide. AI suggests; it doesn't settle a conflict or approve anything.

How does the specification get checked?

Each item goes back to the experts whose answers it came from, to confirm "Right" or say what's wrong. Before sign-off, Mochlion also checks the spec for gaps, contradictions and anything a builder would have to guess. Each one goes back to the right person, and people act on each finding or set it aside with a reason.

When is it Build Ready?

A project is Build Ready when there are no open conflicts, the requirements can be tested, someone has agreed to own the application after it's built, and the spec is signed off. If something stands in the way, the readiness check names it and where to fix it.

What do I get?

The Build Specification as PDF, Word or Markdown, a one-page summary for the owner, and an AI build package that coding tools can read directly. Every item has a trace ID. See a sample.

What happens at handoff?

You hand the specification to your builder, your own team or an outside practitioner. Once they acknowledge it (or 5 days after it's delivered, if they haven't), a 90-day window starts: changes you approve during it are included, and each one produces a new version with a report of what it affects. After that, a major revision needs a new credit.

Mochlion doesn't build, host or run the application. Handoff is where our part ends.