# Serras

> AI software delivery for agencies and product teams. Build ambitious software. Reach the market sooner.

Symphony does the work. Studio is where your team directs it. Podium is where your client sees it. Conductor is the admin console Serras runs behind the suite. Symphony runs inside the customer’s own Claude Code or Codex account, so AI usage stays on the customer’s plan. Cursor and other integrations are upcoming. Waypoint is the work tracker built into Serras: a simpler alternative to Jira, at no additional cost. Serras builds web apps, native iOS and Android apps, desktop apps, and APIs.

## Product information

- [Suite overview](https://serras.ai/index.md): Products, engagement options, and common questions.
- [Everything on one page](https://serras.ai/llms-full.txt): The full public content of this site in one file.
- [Serras Symphony](https://serras.ai/symphony/index.md): The core delivery system. Studio, Podium, and Conductor connect it to the people around the work.
- [Serras Studio](https://serras.ai/products/studio/index.md): The desktop workspace for directing Symphony workflows with Claude Code and Codex.
- [Serras Podium](https://serras.ai/products/podium/index.md): The client view of the project: progress, decisions, and released work.

## How Serras works, and who it is for

- [How Serras delivers](https://serras.ai/delivery-line): How Serras delivers software as one line: shape, build, check, release and improve. Nine stages to the first release, checks before and after the build, and one record.
- [Integrations](https://serras.ai/integrations): Symphony runs inside your own Claude Code or Codex account and works with Jira, Sentry, UserSnap, Figma, GitHub, Vercel, Supabase, ElevenLabs and Google Veo. Waypoint, the tracker built into Serras, is a no-cost alternative to Jira.
- [For agencies](https://serras.ai/for/agencies): Serras runs delivery from the client's brief to the release, plus the proposals, status updates and handoff around it. Your agency keeps the client and makes the decisions.
- [For product teams](https://serras.ai/for/product-teams): Symphony plans, designs, builds and checks the work inside your own Claude Code or Codex account, with Jira-native tickets and a record of every decision.
- [For founders](https://serras.ai/for/founders): Serras turns notes or long documents into a designed, built and checked product, and helps with the brand, the pitch and the budget around it.
- [Existing products](https://serras.ai/existing-products): Retrofit, upgrade, redesign or replace a live product with Serras, without losing its history or its requirements.
- [How engagements work](https://serras.ai/engagements): Three ways to work with Serras: run it yourself, have Serras deliver your product, or partner on a new venture. No public prices; every engagement is scoped to the project.
- [Why not just use Claude Code?](https://serras.ai/compare/claude-code): You should use it. Symphony runs inside it. What Serras adds around a coding agent when the product does not exist yet: decisions, design, checks, a record, and the work around the product.
- [Traditional delivery vs Serras](https://serras.ai/compare/traditional-delivery): The same goal, a product people can use, by a different path: decisions recorded, checks before release, and training and documentation shipped with the release.
- [What’s new](https://serras.ai/whats-new): What changed in Serras products each month, and why it helps. October 2026: fewer steps per build, faster large Waypoint plans, and long runs stay open.
- [Build stories](https://serras.ai/evidence/builds): Products built with Serras, each told from the build’s own record: what it is, where to find it, how it was built, and how long it took.
- [How we built Podium](https://serras.ai/evidence/podium): One person directed Symphony from the brief to Podium's first phase in production in 17 days: every core stage, 88 acceptance criteria, 1,929 browser checks passed, and 57 decisions on the record.
- [How JTN Local was built](https://serras.ai/evidence/jtn-local): JTN Local, the local-news site from Just the News, went from a brief to its first live release in 66 hours: 32 requirements approved, 44 screens designed, and one person directing Symphony.
- [How Lumos Throughline was built](https://serras.ai/evidence/lumos-throughline): EIGHT32, a Serras development partner, built Lumos Throughline in 25 days: 76 requirements and 280 acceptance criteria approved before the build, 53 screens designed, and one person directing Symphony.
- [Workflow library](https://serras.ai/workflows): Symphony runs 80+ workflows. These are the ones teams use on client and product work, grouped by the five phases of the delivery line, each with what you give it, what you get and who decides.
- [Workflow: Setup](https://serras.ai/workflows/setup): Start every project with its platforms, tools and client evidence ready. Use it first on every project, new or existing.
- [Workflow: Discovery](https://serras.ai/workflows/discovery): Discover what your product can really be, then agree on it. Use it after Setup, before brand, analysis or design work begins.
- [Workflow: Brand builder](https://serras.ai/workflows/brand-builder): Get a new brand identity for your product, from logo to brand book. Use it after Discovery when your product needs a new identity.
- [Workflow: Brand import](https://serras.ai/workflows/brand-import): Keep your established brand intact, with every rule traced to its source. Use it when your client already has a brand that the product must follow.
- [Workflow: Analysis](https://serras.ai/workflows/analysis): See how the product must behave, and what could block it, before design. Use it after Discovery to settle behavior and technical questions before Scope.
- [Workflow: Scope](https://serras.ai/workflows/scope): Lock exactly what the product must do before design starts. Use it after Analysis, before any design work begins.
- [Workflow: Design](https://serras.ai/workflows/design): See your whole product designed, every screen and state, before anyone writes code. Use it after Scope is approved, or in presale mode to support an estimate.
- [Workflow: Delivery plan](https://serras.ai/workflows/delivery-plan): Know what gets built, in what order, and how each piece is tested. Use it after Design is approved, or in presale mode to size workstreams for an estimate.
- [Workflow: Verification](https://serras.ai/workflows/verification): Prove every requirement and screen has a task and a test before coding starts. Use it after the delivery plan, as the last check before implementation.
- [Workflow: Implementation](https://serras.ai/workflows/implementation): Get working code built to your approved design, checked wave by wave. Use it once Verification confirms the plan is ready to build.
- [Workflow: Design validation](https://serras.ai/workflows/design-validation): Confirm the built product looks, moves and behaves like the approved design. Use it after implementation to catch drift from the approved design.
- [Workflow: Feature validation](https://serras.ai/workflows/feature-validation): Prove each feature passes its approved acceptance tests, with evidence you can rerun. Use it after implementation; tests that write data never run against production.
- [Workflow: Functional validation](https://serras.ai/workflows/functional-validation): Find the problems scripted tests miss by exploring real user journeys. Use it after implementation, alongside the other checks, before release.
- [Workflow: Staging deploy](https://serras.ai/workflows/staging-deploy): Put a verified build on staging, with proof that it works. Use it when a validated build is ready for review in a staging environment.
- [Workflow: Retrofit](https://serras.ai/workflows/retrofit): Bring an existing product into Serras without losing approved work or history. Use it for an existing or partly built product you want to continue in Serras.
- [Workflow: Upgrade](https://serras.ai/workflows/upgrade): Add or change requirements in your product without losing what is already approved. Use it when a product with an approved plan needs new or changed features, before or after launch.
- [Workflow: Redesign](https://serras.ai/workflows/redesign): Give a working product a new look without changing what it does. Use it when a built or live product works well but its interface needs replacing.
- [Workflow: Site upgrade plan](https://serras.ai/workflows/site-upgrade-plan): Plan a replacement marketing site with a decision for every piece of current content. Use it when a live marketing site needs replacing; the new site is then built through the core stages.
- [Workflow: Rebuild spec](https://serras.ai/workflows/rebuild-spec): Get a detailed spec for rebuilding your legacy system on a new stack. Use it when you are replacing an old system and need everything it does written down first.
- [Workflow: Codebase comparison](https://serras.ai/workflows/codebase-comparison): Decide what to keep, port or retire across two codebases, with evidence. Use it when two codebases overlap and you need to decide what survives.
- [Workflow: Content migration](https://serras.ai/workflows/content-migration): Move your old site’s full article archive into Sanity, checked item by item. Use it when a website is being replaced and its articles must move to the new site.
- [Workflow: Scenario testing](https://serras.ai/workflows/scenario-testing): See which scenarios break your running app, with a fix ticket for each failure. Use it when your Jira project already holds a set of structured test scenarios.
- [Workflow: Launch check](https://serras.ai/workflows/launch-check): See how close your product is to launch and where to start. Use it when a product is close to launch and you need the remaining work in one list.
- [Workflow: Issue intake](https://serras.ai/workflows/issue-intake): Turn production errors and user bug reports into ready-to-build fix tickets. Use it when production errors or user bug reports need to become planned fixes.
- [Workflow: Pitch deck](https://serras.ai/workflows/pitch-deck): Make your case with a deck where every claim is sourced and approved. Use it when you need a sales, fundraising, stakeholder or product explainer deck.
- [Workflow: Patent drafting](https://serras.ai/workflows/patent-drafting): Find the patentable ideas in your product and draft applications for attorney review. Use it when your product includes technical ideas you may want to patent.
- [Workflow: Office action response](https://serras.ai/workflows/office-action-response): Answer a patent office rejection with a draft response ready for attorney sign-off. Use it for a non-final office action with rejections under sections 102, 103 or 112.
- [Workflow: Operating budget](https://serras.ai/workflows/operating-budget): Know what your product will cost to run for one to three years. Use it at any stage once requirements exist, to plan running costs.
- [Workflow: Project estimate](https://serras.ai/workflows/project-estimate): Give your client a full-cycle estimate grounded in measured spend and past projects. Use it after design and delivery planning, or after a presale design, to price the project.
- [Workflow: Build estimate](https://serras.ai/workflows/build-estimate): Price the build ticket by ticket, with a timeline and monthly payment plan. Use it after Verification and before implementation, when you are ready to commit to a build price.
- [Workflow: Valuation](https://serras.ai/workflows/valuation): Get an indicative value range for your company, based on researched market multiples. Use it for an early, indicative view of value, not as a formal appraisal.
- [Workflow: Acquisition review](https://serras.ai/workflows/acquisition-review): Justify an acquisition price or funding ask with evidence from the product itself. Use it when a buyer or your stakeholders need evidence that the product is worth the price.
- [Workflow: Contract drafting](https://serras.ai/workflows/contract-drafting): Get a draft services agreement and statement of work for your client engagement. Use it when an engagement is agreed; have legal counsel review both drafts before signing.
- [Workflow: Proposal site](https://serras.ai/workflows/proposal-site): Give your client one branded link to review your whole proposal. Use it when your proposal is ready for client review; leave sensitive material out.
- [Workflow: Status reporter](https://serras.ai/workflows/status-reporter): Keep your client informed with fact-checked status decks and weekly emails. Use it for regular client updates while delivery is underway.
- [Workflow: Product explainer](https://serras.ai/workflows/product-explainer): Show end users what your product does and why it matters, in plain language. Use it when end users, not investors or executives, need to understand the product.
- [Workflow: Training builder](https://serras.ai/workflows/training-builder): Train each audience on your web app with screenshots from the running product. Use it before rollout, when each user role needs to learn the web app.
- [Workflow: Documentation writer](https://serras.ai/workflows/documentation-writer): Get technical documentation of your codebase, written from the code itself. Use it before a handoff, or whenever the code has moved ahead of its docs.
- [Workflow: Architecture diagram](https://serras.ai/workflows/architecture-diagram): See how your system fits together in an interactive, exportable diagram. Use it when clients, engineers or reviewers need a clear picture of how the system is built.
- [Workflow: Delivery showcase](https://serras.ai/workflows/delivery-showcase): Walk your client through everything you delivered, with the evidence behind it. Use it at handoff, when your client wants to see what was produced and how it was checked.
- [Workflow: Logo generator](https://serras.ai/workflows/logo-generator): Explore several logo directions as clean vector files you can review side by side. Use it for a quick, standalone logo exploration; Brand builder covers a full identity.
- [Workflow: Brand from website](https://serras.ai/workflows/brand-from-website): Make new work match an existing brand, captured from its live website. Use it when a client’s brand lives on their website rather than in a brand guide.
- [Workflow: Marketing site plan](https://serras.ai/workflows/marketing-site-plan): Plan a new marketing site from your product’s facts, competitors and inspiration sites. Use it before building a new marketing site; the site is then built through the core stages.
- [Workflow: Video production](https://serras.ai/workflows/video-production): Turn a brief into a narrated film in your brand, approved scene by scene. Use it for a launch film, a product promo or a brand story.
- [Workflow: Messaging writer](https://serras.ai/workflows/messaging-writer): Replace generic copy with plain, benefit-led messaging you can back up. Use it when your product copy sounds generic or makes claims you cannot prove.
- [Workflow: Brainstorm](https://serras.ai/workflows/brainstorm): Find and score the next opportunities for your product, backed by evidence. Use it when an existing product needs an evidence-based view of what to build next.
- [Workflow: Requirements writer](https://serras.ai/workflows/requirements-writer): Turn a rough idea into researched feature requirements, ready for Discovery. Use it when you have an idea but no written requirements yet.
- [Workflow: Enhancement roadmap](https://serras.ai/workflows/enhancement-roadmap): See which improvements are worth the investment, ranked by cost and benefit. Use it when the product works and you are planning the next round of improvements.
- [Workflow: Client feedback](https://serras.ai/workflows/client-feedback): Turn your client’s review notes into one de-duplicated, build-ready backlog. Use it after a client review, when feedback arrives in many formats.
- [Workflow: Improvement loop](https://serras.ai/workflows/improvement-loop): Turn repeated delivery mistakes into permanent checks, proposed for your approval. Use it periodically to learn from defects that keep slipping through.
- [Workflow: UX audit](https://serras.ai/workflows/ux-audit): See where real users would struggle, with video, before they do. Use it before a redesign, or when users report friction.
- [Workflow: Figma sync](https://serras.ai/workflows/figma-sync): Keep the approved designs in step with changes made in Figma. Use it when your designers keep working in Figma during delivery.

## Optional

- [The film, 97 sec](https://youtu.be/bmtxXfAsixM): A 97-second film about how Serras turns a new idea into a working product: your team shapes it and makes the decisions that matter, Symphony builds it in waves and performs validation after every wave, and your client sees each release in Podium. Podium itself was built with Serras; its first phase went live in seventeen days.
- [Explainer video, 7 min](https://youtu.be/MGZXB3jjrw4): How Serras turns a new idea into a working product: shared project knowledge, product direction, analysis and brand, an interactive design you respond to, a coordinated build checked against what you agreed, and the business materials around it. Studio puts the process in your team's hands.
- [Teaser video, 90 sec](https://youtu.be/p-XGgQBgVSw): The same story in ninety seconds.
- [Serras at Work, episode 1: Design, 3 min](https://youtu.be/VFB_kbKXCb4): Episode 1: the Design workflow, from a short brief to a live site that matches its approved design. Its article: https://serras.ai/workflows/design
- [Serras at Work, episode 2: Discovery, 3 min](https://youtu.be/cdVKvCs0X8U): Episode 2: the Discovery workflow, from scattered sources to one approved answer. Its article: https://serras.ai/workflows/discovery
- [Serras at Work, episode 8: Brand builder, 3 min](https://youtu.be/QUCWSdMSjfM): Episode 8: the Brand builder workflow, from real choices to a brand your whole team can use. Its article: https://serras.ai/workflows/brand-builder
- [Serras at Work, episode 13: Analysis, 3 min](https://youtu.be/8HSXB14Swgg): Episode 13: the Analysis workflow, from your approved Discovery to one approved analysis that every later stage starts from. Its article: https://serras.ai/workflows/analysis
- [Results](https://serras.ai/evidence): Beta white-glove customer delivery experience, with a separately labeled sample workflow.
- [Technical assurance](https://serras.ai/assurance): How decisions, checks and history stay attached to the work.
- [Development partners](https://serras.ai/partners): The preferred delivery network.
- [Serras Ventures](https://serras.ventures): The founder partnership stream. For selected startups, Serras reduces development fees in exchange for negotiated equity participation.
- [Talk to Serras](https://serras.ai/inquiry): Platform, services, and venture inquiries.