Question 1

What does Inter Web Services actually do?

Accepted Answer

Two things that are usually bought separately. We build custom software — web applications, mobile apps, integrations, cloud platforms, and data products — and we provide business consultancy covering technology strategy, process design, and transformation delivery. Most engagements involve both, because deciding what to build is usually harder than building it.

Question 2

How does a first conversation work?

Accepted Answer

Email sales@interwebservices.co.uk or use the contact form with a short description of the problem. We reply within one business day and arrange a 30–45 minute call to understand the situation. That call is free and carries no obligation. If we are not the right firm for the work, we will say so and point you toward a better fit where we can.

Question 3

Do you work with small businesses or only large organisations?

Accepted Answer

Both, though the engagement shape differs. Smaller organisations typically start with a discovery piece or a focused build; larger ones tend to begin with a strategy or process engagement before delivery. The practical constraint is budget realism rather than company size — we would rather tell you a project is under-funded than start it and stop halfway.

Question 4

Are you based only in the UK?

Accepted Answer

We are a UK company operating from London EC1V 2NX, and engagements are led from the UK. Delivery is remote-capable, and we work with clients internationally. On-site workshops are arranged where discovery, training, or stakeholder alignment genuinely benefits from being in the same room.

Question 5

Can you take over a project another supplier started?

Accepted Answer

Yes, and it is a common request. We begin with a technical audit covering code quality, dependency risk, infrastructure access, and documentation gaps, then give you an honest assessment: continue, remediate, or rebuild. The audit is a standalone deliverable, so you can act on it with or without us.

Question 6

How do you price work?

Accepted Answer

Fixed fee for defined scope, monthly rates for dedicated teams, day rates against a capped budget for exploratory work, and monthly retainers for support and advisory. Which model applies depends on how well-understood the scope is. We explain the trade-offs of each rather than defaulting to whichever suits us.

Question 7

Why won't you quote a fixed price straight away?

Accepted Answer

Because a fixed price for undefined work is guesswork, and guesswork gets recovered later through change requests. A short paid discovery produces a specification, an architecture, and a credible number. You own that output and are free to take it to another supplier — that is a reasonable outcome and it happens.

Question 8

What does a typical project cost?

Accepted Answer

It varies too much for a headline figure to be useful. A focused discovery engagement is a few weeks of effort; a substantial custom platform is several months with a team. What we can commit to is giving you a realistic range early in the first conversation, so nobody invests time in a project that was never going to be affordable.

Question 9

What happens if requirements change mid-project?

Accepted Answer

On sprint-based engagements, priorities can be reordered each sprint at no extra cost — that is a deliberate benefit of the model. On fixed-scope work, changes go through a written change control with cost and schedule impact stated before anyone proceeds. What we do not do is absorb scope silently and then present a surprise at the end.

Question 10

Will you sign an NDA?

Accepted Answer

Yes. A mutual NDA is standard before discovery and we are happy to work from yours or provide ours. All engagements also run under a signed statement of work setting out scope, acceptance criteria, IP ownership, and commercial terms.

Question 11

How long does a project take?

Accepted Answer

Discovery is typically one to three weeks. Design is two to four. Build ranges from six weeks for a focused application to twenty or more for a substantial platform, delivered in two-week sprints with working software demonstrated at the end of each one. You will have a milestone plan before build begins.

Question 12

How do you decide which technologies to use?

Accepted Answer

By what fits the problem, what your team can maintain, and what will still be supported in five years — in that order. We have a deliberately conventional stack because unusual choices become expensive for whoever inherits them. If you already have a standard, we work within it rather than arguing for ours.

Question 13

How do you keep us informed during delivery?

Accepted Answer

A written weekly update covering progress, budget consumed, risks, and anything we need from you, plus a sprint demo every two weeks where you use what has been built. You have access to the ticket board throughout. Risks are raised as soon as we see them, not once they become unavoidable.

Question 14

How is quality assured?

Accepted Answer

Peer code review on every change, automated test coverage appropriate to the risk of each component, continuous integration that blocks broken builds, and accessibility testing against WCAG 2.2 AA. Before launch there is a formal user acceptance testing phase with your sign-off.

Question 15

Do you use AI to write our software?

Accepted Answer

We use AI tooling to accelerate routine engineering work, and every line that ships is reviewed by a named engineer who is accountable for it. Where a client's contract or policy restricts AI-assisted development or the handling of their code, we honour that restriction and confirm it in the statement of work.

Question 16

Who owns the code and the intellectual property?

Accepted Answer

You do, on payment. Source code, designs, documentation, and infrastructure accounts are yours, held in repositories and cloud accounts under your organisation from day one. We retain no licence over your product and use no proprietary framework that requires us to keep it running.

Question 17

What happens after launch?

Accepted Answer

Most clients move onto a support retainer covering monitoring, incident response under an agreed SLA, security patching, dependency upgrades, and an allocation of improvement time each month. If you would rather your own team took over, we complete a documented handover including runbooks and a knowledge-transfer period.

Question 18

What are your support response times?

Accepted Answer

Retainers are tiered. A priority-one incident — the system is down or unusable — carries a defined response target measured in hours, with lower-severity items handled within agreed business-day windows. Exact targets are set in the service schedule, and we report against them monthly.

Question 19

How do you handle data protection and security?

Accepted Answer

We process personal data as a processor on your instructions under a data processing agreement, apply least-privilege access, encrypt data in transit and at rest, and keep data within agreed jurisdictions. Our practices are aligned to ISO 27001 principles and UK GDPR obligations. We are explicit about what we are aligned with versus formally certified for.

Question 20

What if we want to leave?

Accepted Answer

Support retainers run on 30 days' notice. Because you already hold the code, accounts, and documentation, exit requires no transfer of assets from us — only a handover call and any outstanding invoices. We designed it that way deliberately.

The questions we are actually asked

Working with us

Commercial & contracts

Delivery & technology

Support & ownership

Question not answered here?

Tell us what you are trying to fix