Web design vs custom web app: which one you actually need
We get the same call almost every week: "I need a new website." About 40% of the time, that's right — a marketing website is the right scope. The other 60% of the time, what the buyer actually needs is a custom web app, and they don't know it yet — until they're eight weeks into a "website" build and realize the contractor can't build the customer login flow they wanted. These five questions catch the mismatch early.
The five questions
1. Does the site let a visitor do anything beyond fill in a contact form?
If visitors can book a calendar slot, place an order, submit a complex multi-step intake, see their own data, leave a review tied to an account — you're past marketing-website territory. A contact form is fine; anything involving the visitor's data or state is not.
2. Is there ongoing data that changes after launch?
Marketing websites have content that changes via a CMS — pages, blog posts, occasional copy edits. Custom web apps have data that changes continuously — bookings being created, customer orders, inventory levels, support tickets. If launch is the start of the data lifecycle (not the end of the build), you need an app, not a website.
3. Do you need user accounts and login?
Auth is the line. A website with login is a web app — period. Even a "simple" login flow drags in password resets, session management, account recovery, role permissions, GDPR / CCPA data handling. If you need users to log in for any reason, scope for app-level work, not marketing-site work.
4. Will admins manage content via the site or via a separate tool?
Marketing websites use a CMS (Webflow, WordPress, Sanity) where admins edit content. Custom web apps have admin panels where staff manage live data — approve orders, mark tickets resolved, adjust user permissions. If you're describing the admin experience and it sounds more like "my team uses this to run the business" than "my team edits copy here," you're in app territory.
5. Are there workflow steps the system should handle automatically?
Marketing websites are stateless: a visitor lands, reads, leaves. Custom apps have flow: a customer signs up, triggers a welcome email, gets matched to a sales rep, schedules a call, the system reminds them at 24 hours, follows up post-call. If you're sketching multi-step workflows where the system carries state across steps, that's a web app.
The decision matrix
- 0-1 yes answers → marketing website. Scope a marketing-web vendor.
- 2-3 yes answers → web app territory. Scope a custom-web-app vendor; don't hire a pure marketing studio for this.
- 4-5 yes answers → definitely a web app. Marketing studios will either decline or bolt on a half-built app and bill you for the broken result.
Why this matters for cost
Marketing websites and custom web apps don't just cost different amounts — they cost different orders of magnitude. A well-built marketing website lands in the low five figures. A custom web app starts in the mid five figures and scales into six figures as the data model and workflows grow. If you're buying a $12k "website" but you actually need a $60k app, you'll either:
- Get a $12k website that doesn't do what you need, and pay another vendor $60k to rebuild it from scratch six months later.
- Pay scope-creep change orders as the gap becomes obvious, ending at $40-50k for a half-finished app.
- Discover the mismatch on the discovery call and re-scope before signing — the cheap and easy path.
Why this matters for vendor selection
Marketing-web studios are good at what they do: visual design, content strategy, conversion optimization, CMS implementation. They generally don't have the engineering depth for a custom web app, auth flows, complex data models, or production AI work. They'll either decline the project or accept it and outsource the hard parts to a freelance dev who isn't accountable to you.
Custom-web-app studios (us, for example) handle the engineering depth but often over-engineer marketing sites. Hiring an app studio to build a brochure site is paying for capabilities you don't need. Match the vendor to the work.
Common confusion patterns
- "It's just a Shopify thing" → e-commerce platforms like Shopify or BigCommerce cover most stores out of the box. You're in marketing-web territory + some Shopify customization, not custom web app.
- "Just login functionality" → there's no "just login." Login is the gateway to web app territory. Even minimal auth changes the security, hosting, and engineering profile of the project.
- "Just a booking calendar" → if the booking creates a real reservation tied to a real customer, you have auth, you have state, you have notifications. App territory.
- "It's like Airbnb but smaller" → smaller doesn't mean simpler. Marketplace apps are some of the hardest builds — two-sided auth, payments, dispute resolution, reviews, trust signals.
When you're not sure
Scope the discovery first; don't commit to a vendor before you know which side of the line you're on. A 20-minute discovery call with someone who builds both can save you the $30k mistake of hiring the wrong type of studio. We do this for free, partly because honest scoping is good business and partly because the wrong-fit project always ends in tears.