Acceptance criteria
The PRD gives each MVP requirement acceptance criteria and checks that say when it is done.
Start technical work with a clearer product brief
Byblos AI helps CTOs and developers start from a clear product brief and a concrete build path. Read the PRD and roadmap, plan the build with Co-CTO in private beta, and start from your own repository or the Production Foundation. Coding agents connected through MCP read the same documents, and credentials stay in Secrets Manager.
Product Manager and the MCP connector start on Free. Co-CTO comes with the Grow and Byblos AI Pro betas, which both open by request: you request access, an administrator approves, then you check out. The Production Foundation is a separate one-time purchase, sold by request.
Free plan · No credit card required
Last updated
The build path, step by step
Step 1
Check the product brief
Review the problem, user journeys, product scope and success measures. Raise ambiguities before turning requirements into technical commitments.
Step 2
Plan with Co-CTO
In private beta, Co-CTO records architecture decisions and quality gates, opens GitHub issues you can assign to developers or AI coding agents, and reviews the pull requests that come back.
Step 3
Build from a solid base
Work in your existing repository or start from the Production Foundation’s three repositories. Connect Claude Code or another MCP client so coding agents read the PRD and roadmap.
From PRD to pull request
The build path from Product Manager to reviewed pull requests
Product Manager produces an approved PRD and roadmap, Co-CTO in private beta records decisions and opens GitHub issues, developers or coding agents pick up the issues, and Co-CTO reviews the pull requests that come back.
What you work with
Open decisions, named
Product decisions still open before the build are listed as gates, each with an owner and a deadline.
Credentials out of prompts
Secrets Manager shares each key one person at a time and records every reveal; MCP never reads the values.
Questions CTOs and developers ask
Can we start from a codebase?
Yes. The Production Foundation is a one-time purchase of $5,900, sold by request: a strict TypeScript Next.js web app, Pulumi infrastructure as code for AWS and an optional FastAPI backend, delivered to your GitHub with their tests, CI/CD pipelines and coding-agent skills. One person holds the licence, for their own projects. Co-CTO also works with an existing repository.
Will Co-CTO replace our engineering workflow?
No. Co-CTO, in private beta, plans and reviews; your team writes, tests and ships the code. It records architecture decisions and quality gates, opens GitHub issues in your connected repository for developers or coding agents, and gives review guidance on the pull requests that come back, so your branches, CI and releases stay yours.
Can my coding assistant read project credentials through MCP?
No. Workspace MCP excludes Secrets Manager, and Byblos AI assistants cannot read secret values. The connection can supply permitted product documents and other accessible project context. Share credentials with authorized people through the dedicated Secrets Manager workflow rather than pasting them into prompts or general project files.
Continue exploring
Choose your next step
Free plan · No credit card required