Step 1: Identify the real bottleneck
Start by naming the bottleneck in plain language. If the problem is trust, clarity, positioning, or lead generation, you probably need a stronger website. If the problem is repeated work, saved data, approvals, collaboration, or automation, you are moving toward a web app. The format should follow the pain, not the exc
Step 2: Choose a website when persuasion is the product
A website is the right investment when the visitor needs to understand, trust, compare, and contact. The work is not “just design.” It is positioning, hierarchy, copy, visual quality, proof, speed, SEO, analytics, and the path from curiosity to qualified lead. A great website turns attention into confidence and gives t
Step 3: Choose a web app when users repeat a workflow
A web app becomes the right shape when people need to log in, manage data, complete tasks, invite teammates, pay invoices, upload assets, track status, or come back repeatedly. The craft moves from persuasion to workflow. You are designing state, permissions, feedback, edge cases, and reliability across many sessions.
Step 4: Use the account test
Ask one simple question: does the user need an account to receive the value? If no, you are likely still in website or landing-page territory. If yes, ask what the account protects or enables: saved projects, private documents, subscriptions, messages, approvals, reports, or billing. An account without a real job adds