Document

System shapes

Not every business problem needs the same kind of build.

System shapes

Not every business problem needs the same kind of build.

One of the easiest ways to waste time is to choose the wrong system shape too early. This page lays out the main patterns we keep seeing.

1. Workflow cleanup

This is the lightest shape.

It usually means tightening the process itself before adding much technology.

Good fit when:

  • the team is still figuring out the right sequence
  • ownership is unclear
  • the current problem is mostly process and follow-up

Typical moves:

  • clarify stages
  • tighten handoffs
  • define response and approval rules
  • document the new flow

2. Automation layer

This is for repeatable steps that are already understood well enough to support.

Good fit when:

  • the workflow is mostly clear
  • the same manual step keeps happening over and over
  • the team needs reminders, routing, syncing, or lightweight automation

Typical moves:

  • notification and reminder flows
  • simple intake or routing automation
  • reducing duplicate entry
  • better visibility into open loops

3. Shared dashboard

This is useful when multiple people need the same view of status and activity.

Good fit when:

  • the business has recurring states and shared ownership
  • the team needs a trusted view of what is open, blocked, or waiting
  • reporting is becoming operationally important

What to watch out for:

  • a dashboard cannot compensate for a broken workflow underneath it
  • if the status rules are weak, the dashboard will be weak too

4. Client portal

This is the heaviest shape of the four.

Good fit when:

  • clients genuinely need self-service visibility
  • approvals, files, updates, or shared records need a client-facing home
  • the portal will reduce real friction, not just look impressive

What to watch out for:

  • a portal increases maintenance and support expectations
  • if the team is not ready to maintain it, the portal becomes a liability

Choosing the right shape

The right shape depends on three things:

  • how clear the workflow already is
  • how often the problem repeats
  • whether the business can maintain the added complexity

When in doubt, start lighter and earn the heavier build later.