Private Limited Company · London EC1V 2NX
How we work
Each phase produces something you own outright. If you take the discovery output to another supplier, that is a legitimate outcome — and it happens.
Delivery process
Durations are indicative and depend on scope. What does not change is that every phase ends with something concrete rather than a status meeting.
We establish what problem is actually being solved, what it costs today, and whether software is the right answer. Occasionally it is not, and we would rather say so now than three months in.
Activities
You receive
Discovery report, costed options, and a recommendation
Architecture and interface design happen together, so what is designed can be built within budget. You review clickable prototypes before engineering starts, when changes are still cheap.
Activities
You receive
Approved prototype, architecture, and statement of work
Two-week sprints with working software demonstrated at the end of each one. You see genuine progress fortnightly, not a status document, and priorities can change between sprints.
Activities
You receive
Tested, deployable increments in a staging environment
Go-live is planned as an event with a rehearsed cutover and a rollback path. Training and documentation land before launch, not afterwards, because adoption is where most projects quietly fail.
Activities
You receive
Live system, trained users, and documented handover
Software is not finished at launch. Under a support retainer we patch, monitor, and improve — with a transparent queue so you always know what is planned and what it costs.
Activities
You receive
Maintained platform with a prioritised improvement roadmap
Engagement models
The right model depends on how well the scope is understood. We will explain the trade-offs rather than defaulting to whichever suits us.
Well-defined scope with a firm budget ceiling
We agree the specification, price it, and deliver against it. Best suited to work where requirements are genuinely stable, and it always follows a discovery phase — fixed pricing without discovery is guesswork dressed up as certainty.
Fixed fee, milestone-based invoicing
Ongoing roadmaps needing consistent capacity
A named team works to your roadmap and adjusts priorities each sprint. You get engineering capacity without recruitment lead times, and the team composition can flex month to month as needs change.
Monthly rate per role, 30 days' notice
Exploratory work where scope will evolve
Billed against time actually worked, with a budget cap and weekly burn reporting so there are no surprises. Appropriate for integration work and modernisation, where the unknowns only surface once you are inside the system.
Day rate against an agreed cap
Strategy, process, and independent review
A fixed-fee advisory piece with a defined question and a written answer — a technology roadmap, a process redesign, or an independent opinion on a proposal you have been given by someone else.
Fixed fee for a defined deliverable
Live systems needing guaranteed response
Tiered SLA cover with monitoring, patching, and a set allocation of improvement time each month. Unused improvement hours roll forward within the quarter rather than simply disappearing.
Monthly retainer by SLA tier
Senior technical judgement without a full-time hire
Part-time technical leadership on a monthly basis: architecture governance, vendor scrutiny, hiring support, and a straight answer on whether the proposal in front of you is reasonable.
Monthly retainer by days per month
Communication
Most project failures are visible weeks before anyone admits to them. Our reporting cadence exists to make that impossible to hide.
Progress, budget consumed against plan, current risks, and anything we need from you. Written to be read by whoever holds the budget.
You use the software rather than watching a presentation about it. Feedback from the demo shapes the next sprint's priorities.
Full visibility of the backlog, what is in progress, and what is blocked. No separate status report is assembled for your benefit.
On support retainers: SLA performance, incidents and their causes, patching completed, and how improvement time was spent.
Our commitments
We will not quote a fixed price for something neither party understands yet. A short paid discovery gives you a real number and a plan you can hold us to.
Source code, infrastructure accounts, designs, and documentation are yours from day one. No licence traps, and no dependency on us to keep the lights on.
Progress is demonstrated as software you can use, every two weeks. Status reports are a poor substitute for seeing the thing run.
Reporting is written to be understood by whoever is accountable for the budget, without a translation layer of jargon in between.
If a deadline is at risk or an approach is not working, you hear it in the next weekly update — not once it has become unrecoverable.
Documentation, runbooks, and knowledge transfer are built into delivery, so your team can take over whenever you choose to.
Common question
Not before discovery, no. A fixed price for undefined work is guesswork, and guesswork gets recovered later through change requests — which is worse for you than an honest number now. Two or three weeks of discovery produces a specification, an architecture, and a figure we will stand behind.
Next step
Send a short description of the problem and we will reply within one business day. The first call is a 30–45 minute conversation with someone senior — free, and with no obligation.
sales@interwebservices.co.uk128 City Road, London, EC1V 2NX, United Kingdom