Pricing
Priced in credits. Sized to your product.
No rate card — every product is different. Pick what you'd want live in your first month and see it in credits. Bryan sends the price with your plan.
What should ship first?
Something else? Describe it on the form and we'll size it.
Ticket sizes
Every ticket has a size. You pay when it ships.
A worked exampleM · 4 credits
Team invites by email
Asked for in Slack. Sized, and approved by you, before anyone started.
- Sized — M, 4 credits, approved in Tengu
- Built — with Claude Code, a reviewed pull request in your GitHub
- QA — passed on a live Vercel preview
- Live — released to production
Credits drawn
when it went live — not before
| Size | Credits | Usually looks like |
|---|---|---|
| XS | 1 | A copy change, a broken link, a tweak to an email |
| S | 2 | A new field or filter, a bug fix, an ad set refreshed |
| M | 4 | A settings page, an onboarding step, a landing page |
| L | 8 | Team invites with roles, a Stripe billing flow, a new integration |
| XL | Split | A new product area — broken into tickets that each ship |
Nothing is bigger than an L. Bigger work is split so every piece ships on its own. Design, ads and launch work are tickets too — they ship when they go live.
Why credits
Hours pay for effort. Credits pay for what's live.
- What you pay for
- HourlyTime someone spentCreditsWork that's live in production
- When you know the cost
- HourlyAfter the work, on the invoiceCreditsBefore the work starts
- When an estimate runs over
- HourlyYou pay for the overrunCreditsWe do — the size was agreed up front
- A slow week
- HourlyBilled anywayCreditsNothing ships, nothing is drawn
- What the invoice shows
- HourlyHours, by personCreditsReleases, each with a link
- What the studio is paid to do
- HourlyStay busyCreditsShip
| An hourly agency | Prizmstack credits | |
|---|---|---|
| What you pay for | Time someone spent | Work that's live in production |
| When you know the cost | After the work, on the invoice | Before the work starts |
| When an estimate runs over | You pay for the overrun | We do — the size was agreed up front |
| A slow week | Billed anyway | Nothing ships, nothing is drawn |
| What the invoice shows | Hours, by person | Releases, each with a link |
| What the studio is paid to do | Stay busy | Ship |
Coming from an hourly retainer? Bryan will size your current backlog on the first call.
Every month includes
- The same team
- The people on your first call are the people on your product a year later.
- A live demo
- Every week you see what shipped, running — not a status report.
- Your code, your accounts
- Your GitHub, your Vercel, your stores. You own all of it from day one.
- A shared Slack channel
- Talk to the people doing the work, not an account manager.
Questions about credits
Anything else, ask Bryan on the first call — or ask the studio.
- What counts as shipped?
- Live in production: a release on Vercel, a build in the App Store or Google Play, a campaign that's running. A preview doesn't count.
- Who decides a ticket's size?
- An AI model in Tengu sizes it from what the ticket asks for, not from who's asking or who's building. You approve it before work starts. If you disagree, we talk before anyone writes a line.
- What if a ticket turns out bigger?
- Its size only changes if what it asks for changes, and you approve the new size first. If we misjudged it, that's on us.
- What if something we shipped breaks?
- Fixing a bug we introduced costs no credits.
- Are calls, planning and QA extra?
- No. They're part of shipping the ticket. Your statement only shows releases.
- Why no price list?
- Every product is different, so every plan is too. Bryan gives you a straight number on the first call.
Contact
Get your price.
Send your picks, or describe what you'd want live first. Bryan replies within one business day with the price, the plan and who'd be on it.
Bryan GauranoFounder & client partner. On every engagement; still ships.
“Prizmstack is the best software development company we've ever worked with — and we've worked with many.”
What happens next
- 01Bryan reads itWithin one business day, with notes on your product.
- 02A 30-minute callWhat it is, what's not working, and whether we're the right team.
- 03Your first month, sizedThe tickets we'd ship first, each with its size and credits, and who'd be on it.