01 / Technical consultancy
First the right route, then build.
Independent advice on software, architecture and product development. So you invest in what works, not in what needs fixing afterwards.
02 / Familiar situations
A choice has to be made. But which one?
A wrong technical choice has an impact for years. Yet that choice is often made under time pressure, based on a single quote or one person's preference.
There is an idea, but no plan yet.
ValidationYou see opportunities for a digital product or platform, but don't know what it costs, how long it takes or whether it is technically feasible.
You have doubts about your current software.
Future-proofingEvery change takes longer than the last. Is further development still responsible, or is rebuilding the wiser option?
Buy, integrate or build it yourself?
Build or buyThere are off-the-shelf packages, custom developers and internal ideas. Without an independent comparison, you choose on gut feeling.
Build your own team or outsource?
OrganisationAn internal team gives control, an external partner gives speed. Which mix suits your budget, risks and knowledge retention?
03 / Independent advice
Advice that doesn't automatically end in building.
We bring your question back to its core, explore different scenarios and translate them into concrete choices. Sometimes that is custom software. Sometimes an existing package, an integration or a smaller change than expected.
Sometimes the best advice is not to build. If so, we will tell you.
04 / Types of advice
What do you want clarity on?
Every question calls for a different approach. Sometimes an idea needs testing, sometimes a broad problem needs to be brought back to a plan, and sometimes an independent judgement is needed on what is already there.
Product strategy, proposition and validation
Test the ideaKnow whether your idea works before you invest in it.
We test the value proposition, target audience and feasibility, if needed with a prototype you can put in front of users straight away.
A good fit when: you have a business case, but don't yet know whether the idea holds up.
Discovery sprint and product roadmap
Scope and planningFrom a broad problem to a plan you can carry out.
Together we define scope, priorities and phasing, and translate that into a roadmap with a realistic investment.
A good fit when: everyone feels something needs to happen, but nobody knows where to start.
Architecture, audit and second opinion
Independent judgementAn honest picture of what is there and what it can carry.
We assess the codebase, architecture, technical debt and scalability, and back up our advice in a clear report.
A good fit when: you are unsure about further development, rebuilding or another party's proposal.
05 / What you get
Advice you can use, even without us.
Good advice has to be usable for your management, your own team and any other suppliers. That is why we don't deliver loose recommendations, but well-founded choices.
| Insight | Choices | Plan |
|---|---|---|
| Analysis of the current situation | Scenarios side by side, with pros and cons | Roadmap and phasing |
| Bottlenecks, risks and technical debt | Buy, integrate or build, with reasons | Indication of investment and lead time |
| What can be kept | Clear advice, not a list of options | Architecture sketch for the chosen route |
06 / Our approach
From question to well-founded choice.
An advisory project is short and clearly scoped. Up front we agree which question needs answering and what you will have in hand at the end.
- Step 1
Sharpen the question
We discuss what you want to achieve, which choice lies ahead and who is involved.
- Step 2
Research
Conversations with users and the team, and where needed a look at code, systems and contracts.
- Step 3
Work out scenarios
We put the realistic routes side by side, with costs, risks and lead time.
- Step 4
Advice and next steps
You get clear advice and a plan. You carry it out with us, yourself or with another party.
07 / Working together
Clear agreements about who does what.
You don't need to supply a worked-out plan. We do need access to the people and information involved in the question.
| Your organisation | TokoWorks |
|---|---|
| Formulates the goal and the question | Researches, analyses and asks critical questions |
| Provides access to people, systems and documentation | Works out scenarios with costs and risks |
| Makes the final decision | Gives well-founded and honest advice |
| Decides who will carry out the plan | Delivers a plan that is usable without us too |
After the advice you are not tied to anything. The plan is yours.
08 / When we are a good fit
An honest match before we start.
Advice only works if there is room for an honest answer. That is why we are clear up front.
Consultancy is a good fit when:
- an important decision about software or technology lies ahead;
- you need a sound rationale for management or investors;
- you are open to advice that turns out differently than expected;
- you want to know what is feasible before you start building;
- someone internally can and will make the decision.
Another party is a better fit when:
- the choice has already been made and you are only looking for confirmation;
- you want guidance through an extensive tendering process;
- you are looking for advice on hardware, networks or office IT;
- there is no room to actually follow up on the advice.
09 / Before we get started
Good to know about technical consultancy.
From independence and duration to what you have in hand at the end.
How independent is your advice if you build software yourselves?
We don't automatically advise building. If an existing package, an integration or a smaller change is better, we say so. After the advice you are not tied to anything.
How long does an advisory project take?
That depends on the question. A clearly scoped project starts from two weeks. After the first conversation you know what to expect.
What will I have in hand at the end?
Clear, well-reasoned advice, the scenarios we weighed up and a plan for the next steps.
Can we carry out the advice with another party?
Yes. The plan is yours and written so that your own team or another supplier can take it forward.
Do you need access to our code?
For an audit or second opinion, yes. For strategy or roadmap questions, often not. We agree on confidentiality up front.