Skip to content
AllFixAI
All insights
StrategyOctober 30, 20255 min read

Website, web app, or internal tool? Choosing the right thing to build

The most expensive mistake in software is building the wrong category of thing. Here is how to tell them apart before you budget.

By AllFixAI

Three different problems

A website exists to be found and to persuade. A web application exists to let someone complete a task repeatedly. An internal tool exists to remove a specific operational cost. They share technology and almost nothing else — different success measures, different content needs, different maintenance profiles.

When a project stalls, it is often because one category was budgeted as another: an internal tool scoped as a website, or a marketing site carrying application logic it was never designed for.

How to tell which one you need

Ask who uses it, how often, and what would be true afterwards that is not true now.

  • Mostly unknown visitors, one-off sessions, persuasion is the goal — build a website
  • Named users returning weekly to complete tasks — build a web application
  • Your own staff, daily, replacing a manual or spreadsheet process — build an internal tool
  • Public content that changes often and must rank — build a website with a real content model
  • A process spanning several existing systems — build the integration first, not a new interface

Buy, configure, or build

Build when the process is a genuine differentiator. Configure when the process is standard and a platform already models it well. Buy and walk away when the process is commodity. The failure mode is building a commodity capability and then maintaining it forever.

A useful test: if you would be embarrassed to describe this software to a competitor, it is probably a differentiator worth building. If they would yawn, configure something off the shelf.

Scope the first version honestly

Whatever the category, the first version should do one job end to end. A complete narrow system teaches you more than a partial broad one, and it gives you something to change based on evidence rather than opinion. Plan the roadmap after the first version is in real hands.

Next article

Running Next.js on Cloudflare Workers: what changes and what does not

Read

Next step

Tell us what needs fixing

Send us the problem in plain language. You will get a considered reply with a recommended next step — not a sales sequence.

We reply to every enquiry within one business day.