Every team,
on one canvas each.
A product team of specialists per workspace, a canvas the whole company can read, and a build that lands in your repo.
Product writes the PRD, design pictures it, engineering interprets it, and QA finds the gap. Here the spec is drawn as boards the moment it exists, everyone reads the same canvas, and the build ships exactly those boards. Your seats direct. The specialists do the craft.
The spec, drawn from one sentence. Two boards nobody wrote a ticket for. That is what the relay below never catches.
Four teams,
four readings of one document.
Every handoff is a translation. Every translation is a sprint.
The PRD said “let them reschedule”. Three teams built three versions of what that meant.
One canvas per product.
Everyone on it.
Shared, edited live, and read by the people who never open Figma.
What Nadia did with them
devischema + book a slot6 minNotes land on the boards.
Nadia turns them into changes.
A stakeholder leaves a note on the reminder. The next morning the SMS line is on the board, and the question it raised is waiting for whoever owns it.
Reminder, the day before
Says
Hi Rita, you are with Maya tomorrow at 09:00. Reply C to cancel or R to move it.
One message. Nobody needs a second one.
Book a slot
ConfirmOpen on Thursday
A patient picks a slot before they make an account, never after.
Maya’s diary · Thursday
Block timeOnly Maya sees this. The front desk gets a separate board with all three.
Every seat on a product team,
and you are in all of them.
Seven specialists on every workspace. Your people direct all of them, in your design system and your voice.
Who this is for
Primary persona: Maria and Tom. Two people sharing one pipeline at a twelve-person company. Maria closes, Tom follows up. Neither has ever opened a CRM they liked.
What they are actually buying
- One list both of them trust, instead of two spreadsheets
- Knowing what to do next without a standup to decide it
- Something that survives one of them being on leave
Pain to mirror in the copy
- “Every CRM is built for a sales team of nine”
- Data entry that costs more than the deal is worth
- Reports nobody on a two-person team reads
Competitive frame
Not competing with Pipedrive on features. Competing on the half hour a week it takes to keep it true. The wedge is two people, one list, not “also works for small teams”.
Objections to answer before the fold
- “We already have a spreadsheet” → show the two-column import
- “What happens when we hire a third?” → seats, not tiers
Pipeline
New dealSorted by last touched. Nothing here is a stage nobody uses.
Visual direction for Anouk
- Mode: light, paper-first. This gets read at a desk, not on a phone
- Accent: one colour, used for state and nothing else
- Type: one humanist sans. Numbers tabular, so columns line up
- Density: eight deals on screen without scrolling
Reference
- Linear’s list density, Stripe’s number formatting
- Nothing that needs a second click to read a deal
Open questions before build
- Does a deal belong to a person or to the team?
- Is “won” a stage or a date?
- Do we show currency on every row, or once in the header?
Billing
Invoices
Plan table and invoice list stay two boards, not one.
keep them apart
Four screens to start: Pipeline, Deal detail, Pricing page, Schema. I have put the words on them, so read them before Devi sees any of it.
added 4 boardsBilling wants a plan table and an invoice list, so that is two boards, not one. Drawing both.
added Billing, Invoices
Nadiaincluded
Jonah
Deviincluded
Theo
Anouk
Rosa
KitYour model account,
or ours. Per workspace.
Where the prompts go is a setting, and the code lands in your repo either way.
On your own model
Over MCP, on the account you already have. Your prompts go to your own provider. Nothing metered by us.
Inside the workspace
No keys to manage. The team signs in and works. Priority builds, seats per person.
There are two ways
to run product across teams.
A document each team reads its own way, or one canvas they all read the same.
- Product writes it.
- Everyone else pictures it, differently.
is found in QA
- Paste the PRD, or say it in a sentence.
- Read the boards, with the data drawn.
- Share the canvas. Design, engineering and the stakeholder read the same one.
- Notes land on the boards. Nadia turns them into changes.
- Approve the look and the words.
- The build lands in your repo, priority queue.
Your design system and your voice,
set once, on every canvas.
Type, palette, the words you use and the ones you do not, the rules every product follows. Every new workspace starts from them, so the tenth product looks and reads like the first.
Every team,
on one canvas each.
Try it on one product, three days free. Then talk to us about the rest.
- All seven agents
- Boards, design and the built app
- Deployed to a live URL
- On your own Claude or Codex
- A workspace per product
- Shared canvases, edited live
- Priority builds, in your repo
- On your model account, or ours
What does HuntingHydra for enterprise include?
A workspace per product, shared canvases edited live, one board for everyone on the team, priority builds, and seats billed per person. Every canvas has the seven specialists on it.
Where does the code live?
In your repo, from the first build. Postgres is yours. Nothing is locked in the product.
Where do our prompts go?
On your own model account, to your own provider over MCP, with nothing metered by us. Or run the agents in the workspace on our API. Your choice, per workspace.
Can stakeholders read the canvas without a seat?
Yes. Anyone with the link can look and leave notes on the boards. Seats are for the people who direct the work.
Can our design system and voice be set once?
Yes. Set the type, the palette, the voice and the rules on the workspace, and every new canvas starts from them.
What does it cost?
The $20 plan is self serve, three days free. Team and enterprise seats are billed per person. Talk to us for the number that fits your team.