October 16, 2026

Website, portal, or custom application?

A practical way to choose between a website, a customer portal, and a custom application — based on the job to be done, not the technology.

Written by Sahad Labs

Start from the job, not the tool

Most disappointing digital projects share one root cause: the technology was chosen before the problem was understood. Before comparing options, finish this sentence: after the project, one specific person should be able to do one specific thing that is hard or impossible today. That sentence usually points to the right category of solution.

A website is for being found and understood

If the main job is to explain an offer clearly and make first contact easy, you need a website: a few focused pages, honest content, fast loading, and clear ways to get in touch. If an existing platform could cover eighty percent of this well, custom software would be expensive decoration — invest in content and design instead.

A portal is for repeated self-service

When customers or partners regularly need to log in and retrieve or submit the same things — documents, statuses, appointments — a portal gives them self-service around your existing process. The signal is repetition: if the same request arrives by email every week, a structured, trackable flow pays for itself in saved time and fewer errors.

A custom application is for unique workflows

When your advantage lives in a process no standard tool models — how you price, produce, coordinate, or deliver — a tailored application can encode it. Start with the smallest version that removes the biggest bottleneck, validate it with real users, and expand from evidence rather than enthusiasm.

Understand first. Build what matters.

Have a question about your own project?

These articles answer common questions — your situation may be different. Tell us what you are trying to accomplish.