The blueprint
Module map, data design, migration plan and phased roadmap.
How we work
One phase at a time. You decide what's next.
Bliq works in gated phases. We start with Discovery, hand you a blueprint that is yours to keep, then build one phase at a time. Each phase is scoped and priced before it starts, and you approve it before we build.
01 · Discovery
What happens in Discovery?
One to two days with your team. We spend 45 to 60 minutes with each person who touches the process, watch how the work really moves, then come back with clarifying questions on day two. Nothing is designed until we have heard from everyone involved.
Managers know how the process should work. The people doing it know how it actually works. We talk to both, because the mess is in the detail.
We map every system you use today, from the accounting package to the spreadsheet on someone's desktop, and rank the processes costing you the most time.
You get
Discovery findings
- Every person heard, not just the managers
- Every system you use today, mapped
- The processes costing the most time, ranked
02 · Blueprint
What's in the blueprint?
A plan you can act on with anyone. It sets out which modules you need, which roles see what, where each piece of data lives, how we move off each current system, and a phased roadmap with a price for each phase. It's yours to keep.
Discovery ends with a blueprint that is yours to keep, whoever builds it. We would rather win the build on merit than lock you in.
You get
The blueprint
- Module map by role
- One source of truth design
- Security and compliance approach
- Migration plan and phased roadmap
03 · Build
How does a phase work?
Each phase is scoped and priced before it starts. You approve it, we build it, and you see it working with your real data. The phase that fixes your biggest pain goes first, so the system earns its keep early and every later phase builds on something proven.
Scope is fixed for each phase. If something new turns up mid build, it goes into the next phase rather than quietly growing this one.
You get
Each phase
- Fixed scope, agreed up front
- Working software at the end
- You decide whether the next phase starts
04 · Run and evolve
What happens after launch?
We stay on to support what we built and tune it as your team uses it. When you're ready, we scope the next phase the same way as the first. You deal with the people who built the system, not a support queue that has never seen it.
Real use shows what to improve. We watch how your team works with the system once it is live and fix what gets in the way.
After launch, one fixed monthly fee runs and improves the whole system: running and monitoring it, fixes, and the steady stream of small changes and refinements, with no hours cap. Only a genuinely new capability is priced separately, and it is agreed before it is built.
You get
After launch
- Support from the people who built it
- One monthly fee for the whole system, no hours cap
- Improvements based on real use
- The next phase only when you want it
What do we keep, whatever happens?
You keep the blueprint, whoever builds it. Your data stays in systems you control. No phase starts without your approval, so you can stop after any one of them and keep everything built so far. Each phase is priced before it starts, so there is no open ended bill.
Your data
In systems you control, not locked inside ours.
The decision
No phase starts without your approval. Stop after any one of them.
Questions about the process
What happens in Discovery?
We spend one to two days with your team, 45 to 60 minutes with each person who touches the process, then a round of follow up questions. You get a blueprint with a module map, data design, migration plan and a phased roadmap, with a price for each phase.
Do we own the blueprint?
Yes. The blueprint is yours to keep, whether we build it or someone else does. It sets out what to build, in what order and what each phase costs, so any capable team could pick it up. We would rather win the build on merit than lock you in.
Can we stop after one phase?
Yes. Each phase is a decision point. You pay for one phase, we prove it works, then you decide on the next. If a phase does not earn the next one, you stop, and you keep what was built along with the blueprint.
How long does it take?
Discovery takes one to two days with your team. Each build phase is sized so you see it working in weeks, not months. You get a timeline for every phase before it starts, and it is part of what you approve, so nothing runs on an open ended schedule.
Who owns what?
You hold a perpetual, irrevocable licence to your instance of the platform, and you own your data and your Blueprint outright. Nothing can ever be switched off or taken back. Bliq owns the underlying platform and may build it for other businesses. Your records and configuration are never part of that.
Start with Discovery
Tell us about the process that is costing you the most time. One of the owners will reply personally.