Proof before commitment
One-Week GIS Prototype
Before you commit a larger budget, see the thing running on data you recognise. One week, fixed price, and you keep the code either way.
Why a prototype and not a proposal
A map can look convincing in a screenshot without showing how it behaves with your data. A focused prototype lets your team try the important interaction and inspect its limits before planning a larger build.
What one week buys
One real view, built properly
A single map view rendering your actual dataset — with a focused layer strategy and interaction model that lets you judge the idea, not a promise of a production platform in one week.
An honest read on performance
What your data volumes do to render and interaction time, where the ceiling sits, and what would have to change to go past it. Including when the answer is that your bottleneck is upstream of the front end.
The code, yours to keep
Handed over in a repository with a short README, whether or not you continue. The prototype is evidence and a starting point, not a finished production system.
Your data, or open data
There are two routes: use a dataset you can share for the project, or agree on relevant open data. We choose the source before work starts so the prototype can answer a useful question without assuming access to confidential information.
What happens after
If the prototype convinces you, the full €2,000 is credited toward the next build. If it does not, you keep the code and the performance findings, and we part on good terms. I would rather you discover a bad fit in one week than after a larger commitment.
What you get out of it
- Evidence instead of assurances, before any real budget moves
- A testable prototype in your browser, not a slide about one
- A clear read on whether your data volumes are a problem, and why
- Working code you keep regardless of what you decide next
What it costs
€2,000
fixed, one week
Credited in full toward the next build if you go ahead. You keep the code either way.
All figures exclude VAT and are invoiced in EUR, company to company, through TARG.DIGITAL SRL.
Is this the right fit?
A good fit if
- You are considering geospatial or real-time work but have not committed budget
- You have been burned before by someone who over-promised on maps
- You can share a dataset — or are happy for me to use open data from your sector
- You want to see the work before you scope a sprint
Probably not if
- You already know exactly what you need built — ask for a scoped build instead
- Something is broken in production right now — that is the emergency deep-dive
- You want a designed mockup rather than working code
How we'd work together
A fixed one-week block, scheduled once we agree the dataset and the single view to build. No hourly billing and no overage.
Questions people ask first
What can you actually finish in one week?
One focused view, done properly, rather than five done badly. The point is not a finished product — it is removing the doubt about whether the hard part is achievable with your data.
We cannot share our data quickly. Is that a blocker?
No. We can agree on relevant open data for the prototype. Any later use of your own data is scoped separately, including access and privacy requirements.
Do we own what you build?
Yes, unconditionally. It is handed over in a repository whether you continue or not. A prototype you cannot keep is a sales demo, and I would rather charge you honestly than dress one up.
Is the fee really credited in full?
The whole €2,000, against the next build. The prototype exists to answer a question, not to function as a paid pitch — if it works, you should not be paying twice to reach the same starting line.
Does this match what you're facing?
Tell me about your stack and where it hurts. If I'm not the right person for it, I'll say so.