Typed 'Web Development Company' Into Google? Read This Before You Book a Call

You typed 'web development company.' You might want a web design company.

Most people who type that phrase into Google are looking for someone to build them a marketing website or an online store. That's a legitimate industry, and it's not what we do. If you need a homepage, a few product pages, and a contact form that emails your sales inbox, keep scrolling past us.

We build custom web applications. Software your team logs into every day to run part of the business — the dispatch board, the quoting tool, the thing that replaced the spreadsheet six people were all editing at once. If that's your problem, keep reading. If it's a website, this article isn't wasting your time, but the rest of our site might.

What we actually build

Portals, dashboards, quoting tools. Internal software that replaces the spreadsheet everyone secretly runs the business on.

Beyond custom web applications, that includes CRMs and internal tools for pipeline, quoting, dispatch, and invoicing. AI and automation for pulling data out of documents and emails, or letting your team search and get answers over your own files instead of digging through folders. Integrations that keep two systems in sync without someone manually re-entering the same order. Mobile apps for field crews and technicians that keep working when a job site has no signal.

None of this shows up in a portfolio the way a nice website does. It's not designed to be looked at. It's designed to survive Tuesday.

If it's a website you need, say so — we'll say so too

We turn down work a specialist would do better. If you need a marketing site or an online store, that's the one thing a web design or e-commerce shop does all day, every day. We'd be learning on your dime, and you'd be paying for our education.

Same principle has us walking away from projects an off-the-shelf tool already solves for a tenth of the price. We'd rather say that on the first call than bill you for discovering it later.

The signals you're actually looking for a custom web application

There's a pattern, and most readers already know which side of it they're on. You're probably looking at custom software, not a website, if:

More than one person needs to use the thing, and they don't all need to see the same data — role-based access, not one shared login. There's an approval step somewhere that currently happens over email or a sticky note, and nobody can prove it happened after the fact. Finance needs a report that currently gets built by hand at the end of the month. Data is trapped in a spreadsheet, or in a system you've outgrown, and it needs to move without anyone retyping three years of history.

If two or more of those are true, you're not shopping for a website. You're shopping for the thing we build.

Why we don't quote it on the first call

We don't give a price on the first call. Nobody honestly can. A number given before anyone has looked at your data, your existing systems, and your approval chain isn't an estimate — it's a placeholder that moves later, and it always moves up.

So we start with a discovery week. Flat $4,800, credited back in full if you continue into the build. Discovery ends in a written scope, an architecture sketch, and a fixed estimate you can actually hold us to.

Ask any vendor at what point their estimate gets pinned down. If the answer is "the first call," ask what happens when it's wrong six weeks in. Ours gets pinned down after discovery, not before. That's the only reason it holds.

What it actually costs and takes

Custom web applications typically run from $45,000, over 10 to 20 weeks, depending on what discovery finds. That covers portals, dashboards, and workflow tools built with role-based access, audit trails and approvals, reporting for finance, and migration of your existing data — plus training so your team can run it without calling us.

Billing runs on milestones: 30% at kickoff, then payments tied to phase acceptance, not to the calendar. Every fixed-scope project includes 30 days of post-launch fixes, because the first month after launch is when real users find the things nobody tested for. Standard terms are Net 14.

Why the stack is boring, on purpose

We build on React, Node, and Postgres. Not because it's exciting. Because it isn't.

Novelty is a cost, paid every year after launch, by the client, not by us. Boring technology, on purpose, isn't a lack of imagination. It's what happens when you plan to still be running this software years from now instead of rebuilding it.

Who owns it when it's done

You own the code outright from day one. Not a license, not a "you can keep using it as long as you keep paying us" arrangement. The code is yours.

The repos live in your organisation, not ours. The infrastructure runs in your own cloud account, not a shared environment we control. That's just how we think ownership should work when someone else paid for it.

Software is never finished

Launch isn't the end of the relationship. It's the start of the part that matters. Every fixed-scope project comes with 30 days of post-launch fixes, because that's when real usage surfaces the edge cases nobody wrote a test for.

After that, care and improvement runs from $4,500 a month, cancel with 30 days' notice. It covers infrastructure as code in your own cloud account, uptime monitoring with a named person on call, and monthly patching, so the thing you paid to build doesn't quietly rot. Treating that as part of the product, not an afterthought tacked onto an invoice later, is the only version of this we think is honest.

If this sounds like your problem

If you read the checklist above and recognized your own spreadsheet, start with a discovery week. It's $4,800, credited back in full if you continue, and it ends with a scope, an architecture sketch, and a number you can actually plan around. The named lead who scopes it with you is the same person who stays through launch.