03 / Custom softwareFuller Function · Services

A tool shaped
around the work.

Custom interfaces, internal tools and focused products. Built around the people, information and decisions that off-the-shelf software does not quite fit.

For teams with a specific operational problem, and founders ready to test a focused product idea with working software.

Actual LineScout demo terminal with filters, a best-price summary and comparison table.
LineScout · web dashboard
FinishSafe native fixture panel showing a simulated workload, normal sleep and the finite Keep Working While Open action.
FinishSafe · native macOS
Actual Back into rotation card, inviting the user to restore a neglected kitchen item. About 20 minutes, inside, low energy.
Go Be Human · web app
Interface depth / LineScoutActual interface · demo data

The screen is one state in a larger piece of work.

A selection needs to survive the move from a busy table to a saved comparison and then to its detail. The record keeps its captured values, source and timing.

Actual interface · demo dataRecorded September 2026
Actual captured comparison: Kansas City Chiefs demo selection, change indicator, quote age and captured price.
Saved comparison · captured valuesSample data
02 / Inside the product

Keep the evidence with the price.

The saved comparison separates captured values from current values, and keeps quote age and changes visible.

View screen

Browse recorded product states from September 2026. Prices and timing are sample data, with no live market feed.

Information

What does it know?

The source, age and limits of a record belong beside the value. Sockeye makes unavailable sources explicit.

Sockeye
State

What happens next?

Arrival, work, interruption and return need deliberate treatment. Go Be Human gives each moment a clear place.

Go Be Human
Authority

Who can decide?

An observation is different from a confirmed result. FinishSafe carries that distinction into its receipts.

FinishSafe
In the workIndependent products · not client engagements

Six tools, six working contexts.

  1. 01

    LineScout

    Web in development

    Comparison with a memory

    A dense dashboard carries captured values into comparison and event detail, keeping time and source context attached.

    A saved price needs a memory.

    Web product · in developmentRead case study — LineScout
  2. 02

    Go Be Human

    Web · iOS in development

    A mobile experience with restraint

    A local-first activity flow has an arrival, an invitation, an away state and a gentle return. Each screen serves the same purpose.

    Design for the moment someone leaves.

    Website draft · web app available · iOS in preparationRead case study — Go Be Human
  3. 03

    Sockeye

    Web · iOS and Android in development

    Software for a working environment

    Sockeye keeps field information, source freshness and unavailable states together. Private logs stay on the device.

    An unavailable source should look unavailable.

    Web field beta availableRead case study — Sockeye
  4. 04

    BenchQuest

    Web in development

    A workshop that remembers the work

    Fictional repair tickets, durable local progress and retrieval practice make study a sequence of deliberate actions. Curriculum and human review remain incomplete.

    Progress is not readiness.

    Owner beta · curriculum in developmentRead case study — BenchQuest
  5. 05

    Tonight

    Web, iOS and Android in development

    From an idea to an evening plan

    A documented mobile/web MVP centers plan creation and social interactions. Runtime, account trust and distribution remain release gates.

    Start with a plan people can understand.

    Mobile/web MVP · in developmentRead case study — Tonight
  6. 06

    FinishSafe

    macOS in development

    Native tools with a clear finish

    A macOS alpha connects finite work to bounded sessions and receipts, separating an observed result from uncertainty.

    “Unknown” is a useful result.

How a project runsThree stages, agreed with you

From the first question to something useful.

  1. 01

    Define the useful slice

    Choose a real task and a small path through it. Agree what the first version must know, do and leave to a person.

  2. 02

    Build the states between screens

    Model the information, permissions and transitions. Make loading, missing data, interrupted work and recovery part of the interface.

  3. 03

    Put it in people’s hands

    Test the prototype against the working context. Refine the flow, plan integrations and hand over a maintainable tool with clear operating limits.

A useful place to begin

Bring the work. We’ll find the shape.

  • The task your current tools make awkward
  • A sketch, spreadsheet or walkthrough of the working day

That can be enough to define a first prototype.

Start a project

Let’s make
something useful.

Bring the idea you’ve been turning over. We’ll find a clear place to begin.

Start a project