Log in Start free

Ship

Ship smarter with customer-led specs.

The live spec lands in Cursor, Claude Code or GitHub over MCP — with customer evidence and repo context attached.

Start free See the product

TandemShipped

Your feedback shipped

Hi Simon,

You told us

“the AI rewrite wiped my teammate's edit while we were both in the same block”

What we shipped

You reported that the AI rewrite overwrote a teammate's edit. We fixed it — block-level locking during rewrites, with queued edits replayed.

Resolve co-edit conflicts in AI rewrites

·· CUSTOMER VOICE ····· +12 SIGNALS ··· URGENCY ↑ ····· $48K CONTEXT ··· CONFIDENCE 82% ····· + feedback.returned ··· evidence linked ····· decision updated ··· repo connected ····· outcome pending ···· PRIORITY 01 ··· CUSTOMER ASK ····· SPEC GROUNDED ··· MCP READY ····· RELEASE SHIPPED ··· RESPONSE signal ····· context ··· evidence ····· decision ··· build ····· outcome ··· memory ····· next ·· MRR ····· churn intent ··· commercial weight ····· customer count ··· confidence ····· linked issue +4 new signals ··· ranking recalculated ····· evidence retained ··· customer response returned ····· ···· PRIORITISE ··· REASON ····· BUILD ··· LEARN ····· PRIORITISE ··· REASON ····· BUILD ··· LEARN

Pull the current truth. Don’t paste a stale snapshot.

Coding agents fetch grounded specs, priorities and feedback on demand, then carry the result back into the system.

Connect over MCP.

Build with context.

Sync the outcome.

Delivery · Ship

The hand-off keeps the customer and codebase attached.

GitHub

Nine repo signals ground every spec — real files, issues and conventions, not a blank page.

Explore GitHub →

Cursor

Hand the spec to Cursor over MCP. The agent pulls it in — no copy-paste.

Explore Cursor →

Claude Code

Hand the spec to Claude Code over MCP. The build starts from real codebase context.

Explore Claude Code →

01 · Spec

The first draft is already written.

One cited artifact: What to Build, Why It Matters, Customer Voice, Files to Touch, Done When.

Explore Specs →

02 · Roadmap

A roadmap that sequences itself.

Two rails show intention and flow; one button sequences work by impact.

Explore Roadmap →

03 · Spec map

Every spec, on the map of your codebase.

Codebase, theme and page views with blast-radius classification.

Explore Spec map →

04 · Ship

The spec leaves Annsa as code.

Connect over MCP; hand grounded work to Cursor or Claude Code.

Explore Ship →

05 · Share Back

The customer who asked is the first to know.

Annsa drafts the follow-up in their context; you review before sending.

Explore Share Back →

Learn more about the Annsa Delivery suite.

Asked + answered.

Q1

How does Annsa connect to coding agents?

Over MCP. Cursor and Claude Code can pull specs, priorities and feedback live.

Q2

Can I still copy a spec?

Yes. Copy-paste remains available; MCP is the live, connected route.

Q3

Does customer context reach the build?

Yes. The spec carries its citations and connected-repo context into the agent.

annsa

Build from what is true now.

Start free with up to 100 pieces of feedback a month.