"Web Development Company" Is Two Different Businesses Wearing One Name

Ask ten agencies what they build and you'll get ten confident answers that mean almost nothing. The term covers two unrelated trades wearing the same job title. On one end: marketing-site and storefront shops. Brochure sites, landing pages, Shopify builds, the stuff a customer sees before they buy something. On the other end: studios that build the internal systems a company runs on. The dispatch board, the quoting tool, the intake form, the nightly reconciliation that breaks quietly and costs real money when it does. Both call themselves web development companies. Both will take your call.

The problem isn't that one is better than the other. The problem is mismatched expectations. That's where projects go sideways: the client asks for role-based permissions and an audit trail, and the vendor has never built either, because they've spent their career making sites that don't need them.

What we actually build

We build the software a company runs on, not the site a customer looks at before they call. That means custom web applications: portals, dashboards, workflow tools. Role-based access so the warehouse manager sees something different than the CFO. Audit trails and approvals, because someone will eventually ask who changed a number and when. Reporting built for finance teams, not just for engineers who think a spreadsheet export counts as reporting.

We migrate existing data. Usually out of the spreadsheet everyone secretly runs the business on. Sometimes out of a prior system nobody trusts anymore.

The stack is React, Node, and Postgres. Typical timeline runs 10 to 20 weeks. Pricing starts at $45k. If that number made you flinch, good. It means you now know roughly what this category costs, which is more than most pages on the internet will tell you.

If what you actually need is a website that explains what your company does and takes a form submission, this isn't the section for you, and we'd rather tell you that now, not after you've signed something.

If you need a marketing site, say so — we'll tell you to go elsewhere

We turn down projects a specialist would do better, or that an existing product already solves for a tenth of the price. A marketing website or storefront is not our work. A specialist will do it faster and cheaper, with better instincts for conversion copy and page speed than we have. We'd be learning on your budget. You'll hear that in the first call, not the third, and not after you've paid a deposit.

Three questions that sort a marketing vendor from a software studio

You don't need to know our stack to sort vendors. Three questions expose the difference fast.

Can you show audit trails and role-based access? A marketing shop will ask what you mean. A software studio has an answer before you finish the sentence.

How do you handle migrating our existing data? If the answer is "we'll figure that out," that's a real answer, just not a reassuring one. You want a process, not an improvisation.

Who owns the code when we're done? Ask this even if it sounds obvious. Most vendors give you a vaguer answer than you'd expect.

The discovery week, and why the estimate holds

Most advice on the internet says "get a detailed scope before you sign." Nobody says who pays for producing that scope, or what happens to the number if it's wrong. We do it as a discrete, paid step: discovery week, flat $4,800, credited back in full if you continue with us. It ends in a written scope, an architecture sketch, and a fixed estimate. Not a range. Not a "typically."

The reason the number holds afterward is structural, not a promise. Estimates come after discovery, not before, which is why we can stand behind them. A vendor who quotes you a fixed price on a first call is guessing. You're the one who eats the guess when it's wrong.

Discovery week is the part of the process that turns a guess into a number we're willing to bill against.

Who owns the code — and why that has to be written down

Client owns the code outright from day one. Repos live in your organisation, not ours. Infrastructure runs in your cloud account, not a shared one we control. No vendor lock-in by design. Not a marketing line. A practice we set up before a single line of code exists.

"You own the code" is a sentence a lot of vendors say and fewer actually structure for. If the agreement doesn't put that in writing from the start, you're trusting a handshake to hold up the day you switch vendors or bring the work in-house. We'd rather you never have to test that trust. Set it up right at kickoff and the question never comes up again.

Boring technology, on purpose

We build in React, Node, and Postgres, and we don't rotate off that stack because something newer showed up at a conference. This is boring technology, on purpose. Novelty is a cost paid every year after launch, and the client pays it: whoever has to hire for the stack, patch it, and keep a developer around who still understands it three years from now. Boring means hireable and documented, long after we've handed you the runbooks.

Excitement is a fine quality in a hobby project. In something your finance team depends on, we'll take predictable every time.

How the money actually moves

A fixed-scope project runs from $28k per phase, billed on milestones — roughly 30% at kickoff, then on phase acceptance. That's it. No hourly surprise line items, no invoice that reads differently than the conversation that preceded it. Terms are Net 14. Every fixed-scope project includes 30 days of post-launch fixes, because the first month after launch is when real usage finds the edges a demo never touched, and we'd rather fix those on our clock than yours.

Software is never finished. That's why care and improvement afterward is its own line item, not a footnote.

If you want ongoing work past launch — patching, monitoring, a named on-call person — that's a separate, plainly priced arrangement under cloud, DevOps and care, not something buried inside the build.

If this is your project, here's the next step

If what you need is a portal, a dashboard, or a workflow tool with real permissions and a paper trail, start with discovery week. It's the entry point for a reason: it turns "we think we need something custom" into a written scope, an architecture sketch, and a fixed number, before either of us commits to more.

A named lead stays with you from that first scoping call through launch. No handoff to whoever's free that sprint.

Typical timeline is 10 to 20 weeks, from $45k. If that's the shape of your problem, we're the right call to make. If it isn't, we'll say so before you spend the $4,800 finding out.