NILMOTECH

Contact

Tell us what you’re building.

Fill this in and we’ll come back with a view on scope, timeline and price — or an honest answer that we’re not the right fit. No charge for the first conversation and no obligation afterwards.

Step 1of5
20% completed

01. Identification

So we know who we’re speaking with when we prepare your scope.

Press Enter ↵ to continue

We reply within one working day. No newsletter, no sequence.

Where we are

Remote-first · London, United Kingdom

We work with teams across UK, EU and US time zones, and we overlap at least four hours with every client.

Elsewhere

What happens next

  1. 01We read the enquiry and reply within a working day.
  2. 02A 30-minute call to understand the goal and the constraints.
  3. 03A written proposal: scope, timeline, price, who does what.

Questions

The things people ask before they commit.

Clear answers about scopes, pricing, handovers, and how we operate. No jargon, no smoke.

Frequently Asked • Updated for 2026

With a scoping call, then a short written proposal covering scope, timeline, price and who does what. There’s no charge for that first conversation and no obligation afterwards. If we don’t think we’re the right fit, we’ll say so and point you somewhere better.

Mostly teams between pre-seed and Series A who need to move faster than their current capacity allows, plus established businesses replacing a site or system that has outgrown itself. The common thread is a decision-maker who can approve a scope without a committee.

Often, yes. We begin with a paid technical review of the existing codebase or campaigns — usually a few days — and give you a written assessment of what’s worth keeping, what needs replacing and what it will cost. That way the decision to continue is based on evidence rather than on our optimism.

Fixed price for defined projects, a monthly rate for embedded teams, growth and remote-pod engagements. You get the number before we start and we don’t quietly absorb scope changes — if the scope moves, we re-quote and you decide.

You do, from day one. Repositories, cloud accounts, ad accounts and data live in your name throughout, and everything is handed over with documentation at the end of an engagement. There’s no hostage-taking and no proprietary lock-in.

You can take it in-house, or keep us on for support and growth. Most clients stay for the growth phase, because the same people who built the product are the ones best placed to measure whether it’s working and adjust it. Either way there’s a proper handover rather than a hand-wave.

Have a question not listed here?

Talk directly to our senior engineering and product team

Let's Talk