Plan the product before anyone codes it

Questions, a spec, an architecture and a build plan. Hand it to any builder.

Meridian 2.4 Private
Makers AlmanacPlanning tool of the year 2026
  • Holloway
  • PennantHealth
  • Quarry
  • NNORTHFIELD
  • .OKUlabs
  • fernhillstudio

Planned in the open

Public plans from people who think before they build. Fork one and make it yours.

Browse all 1,284

Most software goes wrong in the first sentence. “A booking app for clinics” hides forty decisions: who can cancel, when a deposit is kept, what happens when a therapist calls in sick. Tycho finds them before your builder does.

A woman leans over unrolled paper plans on a wooden table that stands on a field of clouds

One sentence in.
A plan anyone can build out.

  1. 01

    Questions

    Tycho reads the idea and asks what a senior engineer would ask. Answer, skip, or mark it as an assumption.

  2. 02

    Spec

    Answers become a written spec: roles, flows, rules, data and what is out of scope. Gaps stay flagged.

  3. 03

    Architecture

    Components, data and integrations, each choice linked to the line of the spec that needs it.

  4. 04

    Build plan

    Milestones, tasks and estimates in build order, ready for a team, an agency or an agent.

Halden Studio/Fysio Nord booking/Questions
IDEAA booking app for physiotherapy clinics: patients book, reschedule and pay deposits; four clinics share five rooms and nine therapists.

01Questions

Q-07

Who books: the patient, the front desk, or both?

Both. The front desk books for walk-ins and phone calls.

Q-08

Do therapists work across clinics?

Yes. Two of nine split their week between two clinics.

Q-09

When can a patient cancel and still get the deposit back?

Decides the refund rules, the reminder timing and one Stripe webhook.

Up to 24 h beforeUp to 48 h beforeDeposit is never refundedMark as assumption
Q-10

What happens to booked sessions when a therapist calls in sick?

11 of 14 answered3 open

02Spec

  1. Overview
  2. Users and roles
  3. Booking flow
  4. Cancellations and deposits
  5. Therapist availability
  6. Payments
  7. Notifications
  8. Data model
  9. Out of scope

4Cancellations and deposits

Patients pay a 20% deposit when they book. Cancelling up to 24 hours before the session refunds it in full; later cancellations and no-shows keep it.

  • The front desk can waive a deposit with a written reason. Each waiver is logged.
  • Refunds go back to the original card within 5 working days.
  • A sick therapist cancels with no charge and offers the next three open slots.
Q-12 · open

Do group classes follow the same deposit rule?

Assigned to Priya

03Architecture

Patient web appNext.js · mobile first Front desk appNext.js · calendar APINode · REST · jobs9 endpoint groups AuthMagic link · staff SSO Postgresbookings, patients, rooms PaymentsStripe · deposits, refunds Calendar syncGoogle Calendar, two-way NotificationsSMS and email reminders spec §4 needsrefund webhook

04Build plan

M1 · FoundationsWeeks 1–2
Roles and staff SSO3d
Clinics, rooms, therapists4d
Patient records3d
M2 · BookingWeeks 3–4
Availability engine5d
Patient booking flow4d
Front desk calendar4d
M3 · PaymentsWeeks 5–6
Deposits with Stripe3d
Refund rules (§4)2d
Receipts2d
M4 · PilotWeek 7
SMS reminders2d
Calendar sync3d
Pilot at Fysio Nord Grünerløkka5d
4 milestones · 36 tasks · 7 weeksReady to hand off

Rigor, written down

The parts of planning that usually live in one person's head get their own place, with an owner and a history.

Q-12Do group classes follow the same deposit rule?
Q-13Who can see a patient’s injury notes?
Q-14Assume Norwegian and English only at launch
Hand-offblocked by 2 open questions

Open questions

Nothing gets quietly assumed. Each gap has an owner, and hand-off waits until it is answered or accepted as an assumption.

D-010Staff sign in with Google Workspace SSOAccepted
D-011One Postgres database for all four clinicsAccepted
D-012Deposits charged at booking, refunded up to 24 hProposed

Decisions log

Every choice with the options considered, the reason, and who made the call. Six months later, you still know why.

Likelihood →Impact ↑
R-02 Clinics' old system has no exportMitigation: CSV import in M1

Risk register

Likelihood, impact and a mitigation for each risk, scored again whenever the plan changes.

spec.mdv5 → v6

Patients pay a full 20% deposit when they book.

Cancelling up to 48 24 hours before refunds it in full.

A sick therapist cancels with no charge.

Versions

Compare spec versions line by line, with the question that changed each line, before anyone builds the wrong one.

Hand it to any builder

Your engineers, an agency, a freelancer or an AI coding agent. Everyone gets the same plan, in the format they already work in.

A woman on one floating rock hands a rolled plan across the gap to a man on another
  • Markdown folderspec, architecture and plan as files in your repo
  • Ticketsmilestones and tasks in Linear, Jira or GitHub Issues
  • Agent packordered prompts and context for Claude Code, Cursor or Codex
  • PDF brieffor an agency quote, with open risks on page one
Hand-off packageFysio Nord booking · v6
14 of 14 questions resolved
12 decisions recorded
6 risks with mitigations

Plans that survive the build

From 212 teams who handed off a Tycho plan between January and August 2026.

fewer change requests in the first month of a build
41%
days from idea to hand-off, median
3.2
questions asked per idea, on average
14
features cut before any code was written
1 in 5
We used to start building on a Monday and find the real requirement on Thursday. Tycho asked about refunds before anyone opened an editor.
Ines MoreauFounder, Larkspur Bookings
It is the first spec our contractors have read to the end. The decisions log alone saved us two arguments a week.
Daniel OkaforCTO, Pennant Health
Fourteen questions. Two of them killed features we would have spent a month on.
Abena OwusuProduct lead, Quarry

Pricing

Start free on two ideas. Viewers and commenters never count as seats.

Free

For trying Tycho on a real idea.

$0forever

Start free
  • 2 active ideas
  • Questions and spec
  • Markdown export
  • Publish public plans

Pro Most teams

For founders, freelancers and small studios.

$24per editor / month

Start a 14-day trial
  • Unlimited ideas
  • Architecture and build plans
  • Decisions log and risk register
  • Linear, Jira and GitHub export
  • Agent packs for coding agents

Team

For product teams and agencies.

$40per editor / month

Talk to us
  • Everything in Pro
  • Shared templates and review
  • Approvals before hand-off
  • SSO and audit log
  • Priority support, 4 h response

Questions,
answered first

Is Tycho a website builder?

No. Tycho stops where building starts. It produces the plan; your team, an agency or an agent builds from it.

Which builders can use the plan?

Any. Exports are plain Markdown, a PDF brief, or tickets in Linear, Jira and GitHub. The agent pack is ordered for Claude Code, Cursor and Codex.

How long does a plan take?

A first spec takes about 20 minutes of answering questions. Most teams reach hand-off in 2 to 4 days, with reviews in between.

What if I don't know an answer?

Mark it as an assumption or assign it to someone. It stays in Open questions, and on the hand-off checklist, until it is resolved.

Can it start from an existing codebase?

Yes. Turn on Import repo and connect GitHub. Tycho reads the code first, so its questions start from what already exists.

Who owns the plans?

You do. Plans are private by default, exportable at any time, and never used to train models.

Start with the questions

Free for your first two ideas. No card needed.

Meridian 2.4 Private