What would it take to build this, and what’s the investment?
The Product Discovery Workshop is how our bigger builds start. You spend up to two days with the people who’d build it, walking through your process, your systems and the product, and you watch every piece get sized in front of you. Within five business days you’ll have a backlog, an estimate and a proposal with a price we hold.
- Up to two days
- Up to 8 of your people
- On site or remote
Priced and ready.
Who is this for?
Companies that know what has to change, but not the investment it needs or what goes in the first release.
Does any of this sound familiar?
- A process is held together by spreadsheets and goodwill.
- Two vendor quotes cannot be compared because they priced different things.
- The board approved the idea and wants a number it can hold someone to.
Not the right fit if
-
The build is small enough for a one-page quote
Book a 15-minute call -
You have not decided what to do yet
AI Readiness Workshop -
You are not sure whether to build at all
Build vs Buy Assessment
What happens in the two days?
Up to two days on-site, or four half-days remote.
- Part 1
On the first morning we walk the process as it runs today, end to end, with the people who run it. We map every step, every hand-off and every place someone copies or checks by hand. In the afternoon we go through your systems with whoever runs them: what exists, what connects and what must not change. We also agree where it is hosted and how it is secured.
- Part 2
On the second morning we design the product. Our designer sketches the user roles, key screens, flows and unusual cases live. Together we draw the line around the first release. In the afternoon our engineer sizes each part in days, in front of you. We show you how project management and contingency are added. You watch the price being built, so nothing in it is a surprise.
- Part 3
On-site it is two full days. Remote, it is four half-days over one to two weeks.
The two days, hour by hour
Day one is about your business. Day two is about the software.
Up to eight people from your side: whoever signs, and the people who do the work. From ours, three: a founder, an engineer and a designer. Remote, the same agenda runs as four half-days.
- Walk the process. The people who do the work show us how it is actually done. The spreadsheet, the inbox, the CRM export, the workaround nobody wrote down.
- Follow the data. Where it lives, who owns it, what is already in your CRM, ERP or LMS and what is not anywhere.
- Map the pain. Hours lost a week, where errors start, what each one costs. Ranked with you, on the wall.
- Draw the boundary. What the software should do, what it should not, what stays in the tools you already pay for.
- Shape the solution. Screens on a whiteboard, the data model, the integrations. What gets built on UnflowUI™ from day one.
- Build, buy, or don’t. An honest comparison against off-the-shelf and low-code. If buying wins, we say so and the workshop is the whole engagement.
- Estimate it. Epics, sprints, and numbers you can take to the board. The first release, and what comes after it.
- Decide. What goes in the first release, what waits, and who signs off. The proposal that follows has the price in it.
What do you leave with?
You’ll get four things. A backlog that breaks the work into big pieces and the small steps inside them, each with a check your team can run to see it’s done. An estimate that shows project management and contingency on their own lines. A proposal with milestones no more than four weeks apart and a maintenance option. And a one-page security summary for your CTO or IT lead.
The backlog, the estimate and the proposal are yours. If you build elsewhere, take them with you. Sometimes the honest answer is that you should not build at all. When that happens, the proposal says so and recommends a platform, low-code or UnflowAI™ instead.
Want this for your team? Talk to us first
Backlog, estimate and proposal
Within five business days: the backlog (epics, stories and a check for each), an estimate by epic and discipline, a fixed-price proposal with milestones, deposit and the maintenance option, and a one-page security summary for the CTO. Delivered in UnflowHub™ (Project and Product Management module) and as PDF.
What do we need from you beforehand?
We need three people in the room: whoever decides, whoever runs the process, and whoever runs your systems. Often one person covers two of those. If none of them can spare two days, the project probably isn’t ready yet, and we’d rather say so now.
An intake form, about 30 minutes. View-only access to the systems involved, with one login per person, which we remove the day we finish. Screenshots or a short screen recording of the process as it runs today. And the list of who is coming and what each person can decide. That is it. The more we see before day one, the more of the two days goes on your product rather than on questions.
Up to 8 of your people
- Whoever signs
- The people who do the work
- The engineers who would build it, from our side
Where does the work live afterward?
In your UnflowHub™ workspace. The intake, the process map, the sketches, the backlog and the estimate all live there. The PDF is a copy of what is in it. The backlog is structured as epics, features and stories, so any team can pick it up. Your access stays after the workshop, whoever builds.
See how UnflowHub™ works
What’s the investment? How is it paid?
A single workflow takes less scoping than a platform that touches four systems, so it needs a smaller investment. We’ll work out which one you have on a free 15-minute call, then send you a proposal.
Per workshop
From $2,500
From $2,000
Up to $12,000, set by scope
From $2,500 with the year-end offer, up to $9,600, set by
scope
- Applies to One workshop, booked by December 15 and delivered by March 31
- BundlesWhichever is better. We never go past 25% off
- To book Free 15-minute scoping call, then a Stripe payment link on an invoice: 50% once you accept the proposal, 50% when we deliver the written output
- Credit All of this fee comes off a build that starts within 30 days of the workshop. A Readiness or Build vs Buy credit comes off this fee, on the same 30-day rule
- Travel Free within 50 miles of Dallas or Austin and 31 miles of Porto. Farther away, a fixed fee for each of the three people we bring
Talk to us first
Fifteen minutes to size the scope.
Tell us what you want to build, and we’ll work out how much scoping it needs. Then we’ll send you a proposal with the price.
The call’s free, and nothing is charged until you accept.
- Day
- Time
- Details
What happens after?
It depends on what you decide about the proposal.
Questions people ask.
Remote or on-site?
Either. On-site is two full days at your office. Remote is four half-days over one to two weeks, so nobody loses two whole days of work.
What if we should not build?
Then the proposal says so, and recommends a platform, low-code or UnflowAI™ instead. That is a useful answer, for an investment of two days rather than a failed build.
How is it invoiced?
After a free 15-minute scoping call, we send a proposal. You pay by Stripe payment link on an invoice: 50% once you accept the proposal, 50% when we deliver the written output. US clients are invoiced by our US entity in dollars. European clients are invoiced by our Portuguese entity in euros, with VAT where due.
How soon can we start?
Usually within two weeks of booking. The pre-work needs to be in three business days before the first day.
What do we keep if we build elsewhere?
The backlog, the estimate and the proposal. They are written so another team can use them. We keep our templates and our method.
Does the price in the proposal hold?
Yes, for the scope above the first-release line, for 60 days. A change of scope is priced as a change, in writing, before anyone builds it.
Why does a quote need two days?
Smaller projects don’t need it: we send a one-page quote within three business days. For anything bigger, a quote without discovery is a guess, and someone pays for the guess later.
Do you need access to our systems?
View-only, to the systems the project touches, with one login per person. We remove it the day we finish.
Can more than eight people attend?
We keep it to eight from your side, because two days of design needs a small room. Others can review the backlog in the workspace afterward.
How is this different from the AI Readiness Workshop?
Readiness decides what to do. Discovery scopes and prices one thing you have already decided to build.
Know the investment before you build it.
Up to two days with the people who would build it, and a backlog you keep.