# Sequo > Sequo is a control plane for vibe-coding: it takes you from one paragraph to a working web app, one step at a time. Sequo writes an ordered plan and the documents behind it into files you keep in your repository, then hands Claude Code or Codex one prompt per step, with every prompt naming the files the agent should read first. You run those prompts in your own coding agent — Sequo does not write your code. ## What Sequo does You describe a project in a sentence or two of plain English. Sequo asks a few focused clarifying questions, then produces an ordered build plan and eight documents that live in your repository: idea, specification, architecture, development plan, decisions, invariants, coding standards, and an agent instruction file — CLAUDE.md for Claude Code, AGENTS.md for Codex. Each step of the plan comes with a prompt written for the agent you chose. You paste it into that agent, the agent writes the code, and you mark the step done. Because the plan and the decisions are files rather than chat history, every session starts from the same written record, and each prompt is scoped to one step. Sequo does not replace the agent instruction file — it writes one, CLAUDE.md or AGENTS.md, as one of the eight documents alongside the seven in docs/. Steps that need something only a person can do — creating an account with a third-party service, putting a key in an environment file — carry a short checklist of those tasks, with per-service guidance. When the agent asks a question back, you can paste what it said and get an answer grounded in your own plan and documents. After the last step, a project can continue: you pick what to build next, from scope you deferred, from suggested directions, or in your own words, and a new phase is planned on top of what already exists, with the documents updated to include it. ## What Sequo does not do - It does not write your code, run it, host it, or test it. Your agent does that, in your editor, on your machine, under your own account with that provider. - It does not run your agent for you, and it does not work unattended. Sequo assumes you show up for every step. - It does not use your content to train AI models. ## Which agents it works with Claude Code and Codex. You pick one when you start a project, and the prompts and the agent instruction file are written for that choice. ## Who it is for Solo builders who ship their own ideas with Claude Code or Codex — often several projects a year, each one started from nothing. Someone who can describe the product they want in a paragraph and would rather begin from an ordered plan than improvise the first few sessions and find out later what the order should have been. It is not for someone who wants the AI to build the whole thing unattended, for someone who will not read a plan before running it, or for someone looking for another chat window — Sequo writes files, not conversation. ## What it costs - Free — $0, no card and no trial clock. 1 project at a time, with the entire flow: the plan, all eight documents, and a prompt for every step. Plans on Free are capped at 12 steps. - Pro — $20/month + VAT. Up to 10 new projects a month, plans sized to the product rather than capped, the ability to regenerate anything that comes out wrong, and continuing a project with a new phase after its plan is finished. Sales tax is added at checkout where it applies. Cancel any time; everything you have built stays accessible. ## Links - Home and product overview: https://sequo.app/ - Pricing, including the full FAQ: https://sequo.app/pricing - Terms of Service: https://sequo.app/terms - Privacy Policy: https://sequo.app/privacy ## Notes Sequo is built in public by a solo founder and runs on its own plan. Billing is handled by Polar as merchant of record. Two analytics tools run and no others. Vercel Web Analytics counts page views for everyone: Vercel describes it as working without third-party cookies, it identifies a visitor by a hash discarded after 24 hours, and it never follows anyone to another site. PostHog runs for every visitor but in one of two modes, decided by the consent banner. Before the visitor answers, and if they decline, it runs cookieless: page views, scroll depth and product events are counted against a hash PostHog computes on its own servers and rotates daily, with nothing written to or read from the device — no cookie, no local storage, no identifier, and no session recording. Only after a visitor accepts does it set a cookie, join their visits into one person, link the account, and start recording. It is hosted on PostHog Cloud EU in Frankfurt. A session recording is a replay of the page as rendered, so it contains the visitor's own project text: the idea, the plan, the documents and the step prompts. Passwords, email addresses and bot-check tokens are masked in the browser before the recording is sent, and recordings expire within 30 days. Every event carries which mode produced it, so the two populations are never mixed. Project ids are replaced with a placeholder in the recorded address for both tools, and every query parameter except referral tags is dropped before anything is sent. The choice can be changed at https://sequo.app/privacy. There is no advertising and no cross-site tracking; see the privacy policy for what is stored and why.