A working app your customers can use, launched in one week.
We design, build, test and launch a functioning application in five days for a fixed $10,000. You own the code, the accounts and a roadmap for what comes next.
For CEOs, CROs, CCOs and COOs at US companies with $5M–$200M in revenue.
A short call with our team first. If your idea won’t fit in a week, we’ll say so.
- Day 1Frame
- Day 2Build
- Day 3Test
- Day 4Iterate
- Day 5Launch
6 days
From spec to a deployed marketplace v1 with 30 database tables and about 470 automated tests.
2×
Qualified leads in three months for a cloud infrastructure startup.
5×
More leads over 24 months for a data science company, after we rebuilt its funnel.
45 days
Six content sites launched on one shared engine.
What does a week and $10,000 get you?
One working application, live in production on your accounts, built around one workflow for one type of user. It’s designed with your users, tested with them twice, and launched with a measurement of the business outcome it should move. You keep the code, the tests and a 90-day roadmap.
- Price
- $10,000, fixed
- Time
- Five consecutive days
- Your time
- About an hour a day
- You keep
- Code, accounts, tests, roadmap
Your best revenue idea is waiting on engineering time.
The roadmap is full, so the new tool, the new offer or the prototype waits another quarter. Meanwhile the version someone built over a weekend works in a demo and can’t be trusted with a customer.
CEOs
who need a working prototype of a new idea in front of customers before committing a team to it.
Chief revenue officers
who can't get developer time for a custom go-to-market tool or a new revenue idea.
Chief commercial officers
who want to test a new offer, market or pricing model with real buyers before a full build.
COOs
who need a vibe-coded app turned into production-grade software the business can run on.
Discovery and research that deliver outcomes, not features.
The sprint uses the practices Pivotal Labs teams used to decide what was worth building. We agree on the one number the app should move before anyone writes code, and everything built that week has to serve it. The five days run back to back, can span a weekend, and take about an hour a day of your time.
Pick a day to see what happens.
Day 1 of 5
Discover the problem, frame the solution
Discovery and framing in one day. We agree on the outcome and the users, list what has to be true, and narrow many ideas to the one solution worth building.
By the end of the day: You approve the story map and the design.
- Goals & Anti-Goals
- What the week is for and what it isn't. Anything on the anti-goal list gets cut on sight.
- Assumptions
- What has to be true for the idea to work, ranked by risk. The build tests the riskiest one first.
- Impact Analysis
- A baseline for the business metric the app should move, so launch can be measured against it.
- Stakeholder Map
- Who decides, who uses it and who it affects, so the right people are in the room on day 1.
- Story Mapping
- The user's path through the workflow, sliced to the smallest version that can move the number.
- Design Studio
- Everyone sketches options, we pick one together and refine it into the design.
What day 1 produces, for example
“Sales reps send a priced quote in under 10 minutes.”
- Today
- Quotes wait on a spreadsheet owner
- Metric
- Time from request to quote sent
- Anti-goal
- Replacing the CRM
- Riskiest bet
- Reps trust the pricing rules
What happens after day 5
The sprint ends with a live app and a question: does it move the number? Answering that is a job for you, the owner, with real users. The next sprint starts from what they actually did.
- You
1. Put the app in front of real users
Invite the people the outcome is about, whether that's customers, your sales team or partners. You own the rollout, since you know who to ask and how.
- You
2. Collect feedback
Watch the metric the app launched with, and note where people get stuck, what they ask for and what they ignore.
- You and Cosmic
3. Relay it to Cosmic
Send what you hear to the Cosmic team as it comes in: quotes, screenshots, numbers. It becomes the input for the next sprint.
- Cosmic
4. Run a second design sprint
Once there's a critical mass of feedback, we start a second sprint from what real users did instead of what anyone guessed.
Everything the sprint includes, for one fixed price.
What you walk away with on day 5
- A functioning application in productionDeployed to your cloud account and your domain, used by real people.
- The source code, with tests and CIIn your repository from the first commit. You own all of it.
- A build tested with your users twicePlus notes on what they did and where they got stuck.
- An outcome metric with a baselineAnd the experiment that measures whether the app moved it.
- A story map and a 90-day outcome roadmapSo your team, or ours, knows what to build next and why.
- A recorded handoff for your teamHow the app is built, deployed and tested.
$10,000Fixed for the full five-day sprint
- No hourly billing and no change orders inside the week
- One core workflow for one type of user
- The Cosmic team runs the sprint from day 1 to launch
Start with a short call. We’ll confirm the idea fits in a week before you pay anything.
What the same result takes other ways.
| Hire an engineer | Agency project | The sprint | |
|---|---|---|---|
| First working version | After recruiting and ramp-up | After scoping and a statement of work | Day 5 |
| Price | Salary, recruiting fees and benefits | An estimate that can move | $10,000, fixed |
| Tested with users | If someone plans for it | Depends on the contract | Days 3 and 4 |
| Code ownership | Yours | Depends on the contract | Yours from the first commit |
| Measured outcome | Up to you | Rarely in scope | Baseline set on day 1, experiment live on day 5 |
Why this works in a week.
“At Pivotal Labs I watched small, balanced teams ship software that mattered by agreeing on the outcome first and testing every day. The sprint packs that discipline into one week, for a fixed price.”
What fits in a week, and what doesn’t.
Good fits
- A quoting, pricing or ROI tool your sales team uses with buyers
- A customer or partner portal around one core task
- A prototype of a new product to put in front of paying customers
- An internal tool that replaces a spreadsheet and three handoffs
- A vibe-coded app that needs tests, security and a real deploy
Not a fit for one week
- Replacing a system of record like your ERP or CRM
- Native mobile apps that need app-store review
- Work that needs a compliance audit before launch
- Ideas nobody on your side can make decisions about daily
Questions buyers ask first.
What can really be built in five days?
One core workflow for one type of user, built properly: authentication, a database, the screens that workflow needs, tests and a production deploy. The day-1 story map decides exactly what's in, and anything that doesn't serve the outcome waits for a later release.
How much does it cost?
$10,000, fixed, for the full five days. There's no hourly billing and no change orders inside the week, and we confirm on a short call that your idea fits before you pay anything.
Who owns the code and the accounts?
You do. The repository, cloud account and domain are yours from the first commit, and nothing runs on accounts we control.
What do I need to bring?
A decision-maker available for about an hour a day, three to five users for the day-3 and day-4 tests, and access to any data or systems the app has to use.
How is it production-grade after one week?
The same way Pivotal Labs teams worked: every story is small, tests are written first, code ships to production every day, and a second person reviews every change. By day 5 the app has been deployed several times already, so launch is routine.
A working app your customers can use, launched in one week.
Fixed at $10,000, launched on day 5, and the code is yours to keep.
A short call with our team first.