Fixed-scope packages
For founders, startups, SMEs, and innovation teams that need a visible result.
- Idea Validation Sprint
- Rapid MVP Sprint
- AI Integration Sprint
- Interactive Prototype Sprint
Pick the right model.
The goal is not to force everything into one service shape. It is to choose the commercial structure that helps you move fastest with the least confusion.
Engineering partner
For agencies and companies that already know what they need and want extra senior delivery capacity.
- Daily or weekly engagement
- Embedded in your team
- Unity, WebGL, full-stack, AI, dashboards
- Flexible delivery support
Long-term product partner
For companies building products over several months that need continuity and strategic technical direction.
- Monthly retainer
- Architecture and product roadmap
- Prototype reviews and implementation support
- Launch and iteration support
What each engagement actually contains.
The three models are not tiers of the same thing. They buy different kinds of certainty, and they suit different moments.
You are buying a decision
An Idea Validation Sprint at £1,500 is a working session with the engineer who would build it, a feasibility review, an architecture outline, a roadmap and a budget estimate. A Rapid MVP Sprint from £10,000 is a two-week build path covering authentication, dashboard, backend, deployment and a demo-ready proof. An AI Integration Sprint from £20,000 delivers one working AI feature, chatbot or automation, deployed and documented.
Use this when the thing you lack is confidence, not capacity.
View the packagesYou are buying hands
Day or weekly engineering support, embedded in your team, across Unity, WebGL, full-stack, AI and dashboards. No discovery phase, no re-litigating the brief — you already know what needs building and you need someone senior enough to build it without supervision.
This is the model most agencies and studios use, usually when they have won work with a technical component they do not staff internally.
Ask about capacityYou are buying continuity
From £3,000 a month for ongoing technical direction: architecture and roadmap, prototype reviews, implementation support, and launch and iteration work. The value is that nobody has to be re-briefed every time the product moves.
Worth it when the product will keep changing for months and the cost of losing context between engagements is higher than the retainer.
View retainersWhich one fits your situation.
Four situations that come up constantly, and the honest answer to each.
“We need approval before we can spend properly”
Start with a prototype or proof of concept, from £5,000. The job is to make the idea visible enough for someone to say yes to it — one journey, working, against realistic content. Everything else can wait until the budget exists.
“We have users lined up and need something real”
A Branded MVP from £20,000. Core features, a polished interface, basic integrations, and enough finish that you would be comfortable putting it in front of a customer rather than a colleague.
“This has to run the business”
A production build from £45,000. Architecture, integrations, QA, deployment, launch support and a codebase somebody else can maintain. The jump in price over an MVP is almost entirely the parts you cannot see.
“We genuinely do not know what we need”
Then buy the £1,500 validation sprint before anything else. It is the cheapest way to find out that an idea is smaller, larger or different from what you assumed — and occasionally that it should not be built at all.
How a project actually starts.
No lengthy discovery phase before anything useful happens. The aim is to get from first message to something you can look at in weeks, not quarters.
Tell us the problem, not the solution
The most useful brief describes what is going wrong and who it affects. “Our engineers cannot see which assets need attention” is far more workable than “we need a digital twin”, because it leaves room for the answer to be simpler than you feared.
A short call to find the real constraint
Usually 15 to 30 minutes. We are looking for the thing that decides everything else: a deadline, a stakeholder who has to be convinced, a system that may or may not have an API, or a budget that has a hard ceiling.
A scope with a number on it
You get back what would be built, what would deliberately not be built, which band it falls in, and roughly how long. If the honest answer is that you should buy something off the shelf or configure a tool you already pay for, that is what you will be told.
Build in visible increments
Something is in front of you early enough to change your mind about. This is the whole point of working in small sprints — feedback in week two is worth more than a perfect specification in week one.
Decide what happens next, on evidence
Every engagement ends with a decision rather than a handover of files: expand, adjust, pause, or stop. Work that ends with “stop, and here is why” has done its job as much as work that ends with a launch.
What clients are really buying.
The technology matters, but the buying reason is usually speed, clarity, and confidence.
Instead of AI
Automate repetitive work, reduce admin, speed up decisions, and make internal knowledge easier to use.
Instead of digital twins
Help engineering and operations teams visualise assets, sites, workflows, and scenarios faster.
Instead of Unity or WebGL
Build interactive products stakeholders can actually use, test, approve, and show to others.
Due diligence
The questions you have to answer internally.
Before anyone can recommend a supplier they have to satisfy a checklist that rarely gets asked out loud. Here are the answers without having to ask for them.
Who actually does the work
Simam Digital is founder-led and staffed per project. A sprint is one senior engineer end to end. A production build adds specialists against a defined scope — a second engineer, technical art, QA — briefed by the person who wrote that scope. What does not change between a £5,000 prototype and a fully scoped operational twin is who holds the architecture.
Continuity through a long build
The person who scoped the work stays on it. Nothing is handed over to people who were not in the room, which is the usual place a six-month build quietly loses the reasoning behind its own decisions.
Code, IP and handover
Source code, documentation, technical handover and IP arrangements are agreed as part of each engagement rather than negotiated at the end. A production build should finish with a codebase somebody else can maintain, and that is written into the scope rather than hoped for.
Confidentiality
A good share of the work sits under NDA, and what the agreement actually covers differs every time. Some case studies here name the client and withhold the site; others withhold the client, the sector and the commercial detail. Either way it is what was agreed, and the same discipline applies to yours.
Clients come back
Four builds for A2RL through Focal Point VR. Four for VLGE / Digital Village. Three through Myriad Global Media, all three of which are case studies on this site. Repeat commissions are the part of a delivery record that is hardest to manufacture.
The company behind it
Simam Digital Ltd, registered in England and Wales, company number 14105316, VAT registration number GB451612810, based in Wakefield and working with UK, UAE and US clients. All prices exclude VAT, which is added where it applies. Client references available on request.
Common questions.
The things people ask before they book a call.
How do I know which engagement model to choose?
By what is uncertain. If the idea itself is unproven, buy a fixed-scope sprint — the point is to reach a decision. If the brief is already clear and you just need hands, buy capacity. If the product will keep changing for months, buy a retainer so the thinking stays continuous.
What is the smallest way to start?
The £1,500 Idea Validation Sprint. It is a working session with the engineer who would build it plus a feasibility review, an architecture outline, a roadmap and a budget estimate. It is deliberately priced so that finding out an idea is not worth building is cheap rather than painful.
Do you work with agencies as well as end clients?
Yes. A good share of the work is delivery capacity for agencies and studios who have already won the brief and need senior engineering on Unity, WebGL, full-stack, AI or dashboards. That is a day or weekly rate rather than a fixed package, and white-label delivery is priced on request.
Why are prices given as starting points rather than fixed quotes?
Because the same-sounding brief can differ tenfold in effort. Integrations, content volume, platform targets, design depth, deployment and how many stakeholders need to review it all move the number. The published figures are honest floors, not anchors to negotiate up from.
What if the project needs to change halfway through?
That is normal, and it is the reason the three models exist rather than one. Fixed-scope work is deliberately small enough that changing direction means starting a new sprint rather than renegotiating a contract. If change is expected from the outset, a retainer is the cheaper structure.
How quickly can something start?
A validation sprint can usually be booked within days. Build work depends on current capacity, which is the honest constraint of a founder-led studio — we would rather tell you the real start date than take a deposit and queue you.
Start with the smallest useful step.
If the idea is early, validate it. If the risk is technical, prototype it. If the brief is clear, bring in engineering capacity. If the product keeps evolving, use a retainer.