Work together
You do not need to know what to build yet.
Bring a problem, an opportunity, a process or an idea. I help work out what is actually needed first, and can then build it as well.
When to bring me in
Especially while things are still unclear.
You do not need a plan, an AI strategy or a list of requirements. Recognising one of these sentences is enough to start.
We lose an enormous amount of time here every week.
We think AI could help here, but we do not know how.
We have a good product idea, but not the technical route.
Our current software is starting to hold the company back.
We have plenty of knowledge and data, but get too little out of it.
We want to develop a digital product alongside our existing business.
We have changed, but our positioning has not changed with us.
We know something has to change, but not exactly what.
From question to result
Understand what really needs to change first.
Sometimes the first question is technical. Often it is not. The real question can sit somewhere else entirely.
Understand
What is actually going on?
Choose
Where is the biggest opportunity or friction?
Design
What has to change or be built?
Build
From idea to a working system or product.
Improve
Learn from real use and keep developing.
Sometimes it starts earlier
Maybe you do not need to build anything yet.
When the question is wider than product or technology, I would rather look at the company first. What still holds, what no longer does, and where new possibilities have appeared?
How personal it is
You bring me on board.
Fores3 is deliberately small. You speak to the person who thinks along, designs and builds, from the first conversation to the moment something works.
I think with you about the question.
I help design the solution.
I stay involved while it is being built.
I keep an eye on what it should return for the business.
“I want to understand why something should be built before I decide how we build it.”
Where I can join
01
Company
Direction, positioning, offering and new opportunities.
02
Product & process
Digital products, customer journeys, processes and unnecessary manual work.
03
Technology
AI, software, automation, data and integrations.
A digital coworker can come out of that as well.
Sometimes an engagement starts with the company and ends in software. Sometimes it is the other way around.
Ways to begin
A few ways to begin.
Same care, different distance. Which shape fits is something we settle in the first conversation.
Fores3 Business Review
Looking again at the company before deciding what changes.
You know something has to change, but not yet exactly what.
A broad, independent look at your company with clear choices and priorities.
Typically within 1 to 2 weeks · From €2,500
Build Together
From direction to working software.
You know what has to be made and want to move from direction to a working product or system.
Working software, built around the real business or user question.
8 to 16 weeks · From €20,000
Product Rescue
Regaining grip on a product that has stalled.
A product or system already exists, but direction, technology or development has stalled.
A clear diagnosis and a route to a product that can move again.
2 to 6 weeks · From €7,500
Private Advisory
Continued involvement where it adds value.
Product, technology and company keep developing and you want me involved on a steady basis.
A steady sparring partner for decisions that are hard to reverse.
Monthly · From €2,500 per month
All amounts exclude VAT. External costs or specialist partners are discussed upfront.
After delivery
What gets built belongs to you.
With software in the tens of thousands, this is the question that rarely gets asked out loud. So the answer is here, not buried in a proposal.
Ownership
The code, the data and the accounts are in your company's name. Not mine, and not on a platform that holds you afterwards.
Handover
At delivery you receive everything you need to carry on: the repository, the environments and the documentation that goes with them.
Maintenance
If you want me involved for maintenance or further development, we arrange that separately. If you would rather take it on yourself or with another team, that works just as well.
No lock-in and no mandatory service contract. I want you to be able to move on, including without me.
How that feels
“It genuinely felt like we were working as one team.”
“Everything he recommends is backed by solid reasoning.”
Questions
What people ask before writing.
No. Most engagements start with a situation that grates, not with a finished brief.
A Business Review looks at the company first and ends in clear choices. Build Together starts once that direction is settled and something genuinely needs to be made.
No. The outcome can just as well be that your own team picks it up, that another partner fits better, or that building is not the right move now.
Yes, often. Sometimes as part of a Business Review, sometimes as a Product Rescue when something has already been built.
A limited number of focused conversations with you and the people who actually decide. What I mainly need is access to the right information, not a lot of meeting time.
Your company does. At handover you receive the repository, the environments and the documentation. Maintenance and further development can be arranged separately afterwards, but that is not a condition and there is no lock-in.
Next step
Just put the question on the table.
You do not need to know the solution yet. That is exactly where we can start.
Rather see what I build first?See cases
