How it works

Six stages, two gates, one pull request.

Ideyo follows the same fixed pipeline for every idea. Each stage has a job, sub-steps you can watch, and documents you keep. Between the gates the agent works on its own; it stops where your decision is needed.

0 · Discover

Decide before you build.

Ideyo researches the problem and the people who have it, the products that already exist (direct, indirect and open source), the market in the places you target, the regulation and the technical feasibility. Every claim carries its source. It scores the idea on seven criteria and writes a verdict: GO continues on its own; PIVOT and NO-GO stop and wait for you, with the reasons and what would change the answer.

Sub-steps

s0.1Problem & users
s0.2Existing products
s0.3Market & geographies
s0.4Regulation & feasibility
s0.5Verdict & names

You receive

discovery/etude-opportunite.md
discovery/VERDICT.md
discovery/sources.md

Sample output

Verdict: GO · 3.9/5

| Criterion              | Score |
|------------------------|-------|
| Problem severity       |   4   |
| Reachable market       |   4   |
| Competition (inverted) |   3   |
| Differentiation        |   4   |
| Technical feasibility  |   5   |
| Regulation (inverted)  |   4   |
| Time to prototype      |   3   |

1 · Specify

Write down what will be built.

From the study, Ideyo drafts the requirements, the user stories, the architecture and data model, and a design brief. Assumptions it had to make are marked as such, and the open questions are batched for you instead of being asked one at a time.

Sub-steps

s1.1Requirements
s1.2User stories
s1.3Architecture & data model
s1.4Design brief

You receive

REQUIREMENTS.md
docs/PRD.md
docs/ARCHITECTURE.md
docs/DESIGN_BRIEF.md

Sample output

## 3. Core features
1. Book a chair: service, stylist, time slot
2. Deposit by card, Wave or Orange Money
3. Salon calendar with no-show tracking
4. SMS and WhatsApp reminders, FR / EN

[ASSUMPTION] Deposit = 10% of the service,
             rounded to 500 FCFA, at least 1,000

Gate 1

Gate 1 · Spec approval

Ideyo stops and notifies you. You read the spec on your phone or your laptop, then approve it or say what to change, in plain words. Nothing is designed until you agree. If you prefer, a project can approve its own gates.

2 · Design

See it before it is built.

Ideyo designs the brand with three logo directions, the colour and type tokens, the components and the key screens on desktop and on mobile, as real HTML and CSS rendered in the app. Iterate with messages such as “warmer colours” or “the booking page needs fewer steps”.

Sub-steps

s2.1Brand & logo directions
s2.2Tokens & components
s2.3Key screens, desktop & mobile
s2.4Flows

You receive

design/brand/
design/tokens.css
design/screens/*.html
design/flows.md

Sample output

:root {
  --brand:  #6B2E5F;  /* plum */
  --ink:    #1B1A1F;
  --paper:  #FBF8F4;
  --radius: 10px;
  --font-display: "Fraunces", serif;
}

Gate 2

Gate 2 · Design approval

The second and last stop. Approve the screens, or ask for another round. Once approved, the design is frozen, and the build has to match it.

3 · Build

Test first, slice by slice.

Ideyo writes the code in vertical slices, each one through every layer (data, API, interface), and writes each test before the code that makes it pass. The working tree is versioned from the first commit, so every step can be reviewed.

Sub-steps

s3.1Scaffold & tracer bullet
s3.2Core slices, test-first
s3.3Remaining slices

You receive

src/
tests/
README.md

Sample output

✓ booking › rejects a slot already taken
✓ deposit › 10%, rounded to 500, floor 1,000 FCFA
✓ deposit › marks the booking paid on webhook
✓ calendar › counts no-shows per stylist

142 passed · 0 failed

4 · Quality

Checked before it flies.

Tests and type checks run when a sandbox is configured. Then Ideyo compares the built screens with the approved design, reviews the code the way a senior colleague would, and runs a security review covering secrets, dependencies, input validation and authentication. Every finding is fixed or written up with a reason.

Sub-steps

s4.1Tests & typecheck
s4.2Design fidelity
s4.3Code review
s4.4Security review

You receive

docs/QUALITY.md
docs/SECURITY_REVIEW.md

Sample output

Security review: 0 critical · 0 high · 2 medium · 3 low

M-1  Webhook signature not verified   fixed
M-2  No rate limit on OTP endpoint      fixed
L-1  Phone numbers in logs              fixed
L-2  CSP allows inline styles           accepted

5 · Ship

Into your own repository.

Ideyo creates a private repository in your GitHub account (or uses the one you name), pushes a branch and opens a pull request to dev, with release notes. You merge it when you are ready. The code is yours, under your account, from the first commit.

Sub-steps

s5.1Push to GitHub
s5.2Pull request to dev
s5.3Release notes

You receive

A pull request to dev
RELEASE_NOTES.md

Sample output

ideyo/booking-flow → dev
feat: booking flow with mobile-money deposits #12

+2,814 −37 · 48 files · all checks passed

What if the verdict is NO-GO? Then Ideyo has done its job. A NO-GO comes with the reasons, the evidence, and what would have to be true for the answer to change. Many ideas deserve that answer, and it is far cheaper to hear it before the code. You can still push the project on with a message, or close it and keep the study.

You stay in control between the gates. Write to Ideyo at any time. Nudge adds a note to the current task, Interrupt stops it and changes course, After this stage queues your message for later. The budget cap stops a run before it overspends, and you can close a project whenever you like.

Start free Try the demo See pricing