Use case

A marketplacewith two sides.

Buyers, sellers, listings and payouts. Adams keeps a build this size on plan and guards the paths that move money.

Lite and Pro
// the problem

What goes wrong

Two products in oneEverything exists twice, once for buyers and once for sellers. A change on one side quietly breaks the other.
Money has to land in the right placePayouts, fees and refunds are the hardest part. A wrong assumption is found when someone is not paid.
// what adams does

What Adams does

Starts from a blueprintPro: answer six questions and get a spec and plan covering goal, user, scope, limits, success and risks.
Holds the plan through the buildPro: the drift gate stops quiet scope growth between the seller and buyer sides.
Guards payment keysLite: keys for your payment provider are caught before they are committed.
// worked example

An example

Settling scope first

Illustrative session.

~/project~/your-project · example
/adams:blueprint
Goal: sellers list items, buyers pay online
Limits: one country, one currency at launch
Risk: payouts to sellers are the hardest part
✓ Spec and plan written
// faq

Questions

Does Adams handle payouts?

No. It reads and checks your code. Payouts are done by your payment provider.

Can I build this alone?

It is possible if scope is tight. A blueprint helps you pick a first version small enough to finish.

Is the blueprint free?

It is Pro.

// related

Keep reading