You came here because
You’re building something new
An existing product you want connected, and no idea where to start.
No picture yet of how it would work, or what it would look like.
You need a number you can defend
No idea yet what it costs, or how long.
Budget approval you can’t get without knowing the architecture first.
Your team is not on one plan
Your engineers have their opinions and your commercial team has a deadline.
Those two have never quite been the same plan.
Any of those, and you’re in the right place. You don’t need to know yet how it should work or what it should look like, because that is the first thing we make, before anything gets built.
What you get
You get 4 things, presented to your decision-making team and usable without us in the room.
1
A visual concept
What your connected product looks like, real enough to show a board.
Not a full design. That comes later, if you decide to build.
2
A technical architecture
How it gets built, what it runs on, how it fits what you have.
Written so another engineering team could pick it up.
3
A product blueprint
Functionality, users, data flow, phasing and roadmap.
The document you take into the budget meeting.
4
An investment overview
What it costs to build, and what it keeps costing after that.
Enough to build a budget on, and enough to defend one.
We can own the UX and technology side of your product. Together our goal is to build a profitable business case.
And when it’s done, it’s yours. Most clients go on to build it with us, but the plan is written to be built by anyone. You’re free after this.
How we work
You send us what already exists
Specs, hardware documentation, user insights and commercial goals, so we don’t spend your workshop inventorying your own company.
2 working sessions with a dedicated facilitator
One on users and context, one on architecture and security, run by people who stay with you after.
We build it out, and we present it
To the people who decide, in one session, with all 4 deliverables on the table.
We can start within 2 weeks
From kick-off to presentation is 6 to 8 weeks.
Your team’s availability for the 2 workshops sets the pace, not ours.
What it takes from you
2 workshops with the people who actually decide, not just the technical contact. Miss the commercial decision-maker and you end up with a plan that still has to be sold internally, which is exactly what this was meant to save you.
The material you already have, sent over before we start.
How Specter started here
Under 12 months
from the first workshop to an MVP on the road
“Let’s build a new bike experience, one that we can already experience in cars nowadays.”
That was the ambition. An s-pedelec with GPS tracking, motion sensors, auto-unlock, a head-up display and a companion app: the things a driver already takes for granted, on two wheels.
They also had the problem every startup runs into. To raise funding you need a budget. To build a budget you need a roadmap. And to build a roadmap you need to have made most of the decisions already.
So we started there. Workshops on the market and the competition to pin down what the product had to do, and what riding it should feel like. We designed the experience for the bike and the app, then worked out feasibility and an architecture that could scale without pricing the MVP out of reach. That budget went into their funding conversations.
Read the Specter case
We’ve also run product definitions for Daikin, Novy, Quatra, Handi-Move and Vandewiele.
See all our work
They already trust us, only your logo is missing
Not sure this is the right place to start?
Services
