Skip to content

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, and tells you so on your phone.

Idea board: Compare ideas before you choose one.1

Before Discover · optional

Compare ideas before you choose one.

Have more than one idea? Put two to eight of them on a board, with the markets they target. Each idea becomes a project that runs Discover and stops at its verdict, GO included. The board shows the verdicts side by side: the average score, the seven criteria, the risks, the smallest product worth testing and a build estimate. Pick one and it moves on to Specify; archive the others, their studies kept. A board can also become a comparison report for a client.

  • Every idea counts as an open project on your plan; on the demo model, a board costs nothing and counts for nothing.
  • The cost of Discover is forecast for each idea before you start the board.
Discover: Decide before you build.

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

  1. s0.1Problem & users
  2. s0.2Existing products
  3. s0.3Market & geographies
  4. s0.4Regulation & feasibility
  5. 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   |
Specify: Write down what will be built.

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. It never stops to ask: where it has to guess, it takes a reasonable default and marks it [ASSUMPTION], so you can review every guess at the gate.

Sub-steps

  1. s1.1Requirements
  2. s1.2User stories
  3. s1.3Architecture & data model
  4. 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 · Spec approval

Gate 1

Gate 1 · Spec approval

Ideyo stops and notifies you, on your phone if you installed the app, or by email. You read the spec wherever you are, 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.

At the gate

  • Every assumption Ideyo had to make is listed, grouped by the document it comes from.
  • Confirm it, reject it or rewrite it. Your decisions go with the approval, and the next stage starts from them; reject one and Ideyo suggests asking for changes so the documents are revised now.
Design: See it before it is built.

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

  1. s2.1Brand & logo directions
  2. s2.2Tokens & components
  3. s2.3Key screens, desktop & mobile
  4. 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 · Design approval

Gate 2

Gate 2 · Design approval

The second and last stop. Review the design’s assumptions the same way, then approve the screens or ask for another round. Once approved, the design is frozen, and the build has to match it.

Build: Test first, slice by slice.

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

  1. s3.1Scaffold & tracer bullet
  2. s3.2Core slices, test-first
  3. 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
Quality: Checked before it flies.

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

  1. s4.1Tests & typecheck
  2. s4.2Design fidelity
  3. s4.3Code review
  4. 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
Ship: Into your own repository.

5 · Ship

Into your own repository.

Ideyo pushes a branch to the repository you picked for the project and opens a pull request to dev (or to the default branch), with release notes. You merge it when you are ready; the code is yours, under your account, from the first commit. If GitHub isn’t connected, the project has no repository or the token can’t write to it, nothing is lost: v1 is delivered as an archive, with a note saying exactly what to fix, and becomes shipped when you run Ship again.

Sub-steps

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

You receive

  • A pull request to dev
  • RELEASE_NOTES.md
  • or the archive, when nothing could be pushed
The GitHub token
Repository access
Only select repositories
Contents
Read and write
Pull requests
Read and write
Administration
Only if you let Ideyo create repositories

Create a fine-grained token on GitHub with these settings, paste it in Settings, then pick each project’s repository from the ones the token can see.

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.

Notifications where you are. Install Ideyo from your browser like an app, on your phone or your computer, and it tells you when a gate is waiting, when a verdict is ready, when a run fails or reaches the budget cap, and when v1 is delivered. Email works for the same moments, and each one can be switched off. While you are watching a project, Ideyo doesn’t notify you about it.

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 projected cost updates with every call, the budget cap stops a run before it overspends, and you can close a project whenever you like.