Avorren · Process · 2026

How a project runs.

The same discipline at three useful sizes: the website plan, a systems diagnostic, and phone reception. Numbers for the focused website live on the plan page after you ask.

Choose the closest door

Start with the change. The process holds after that.

You do not need to diagnose the fix. The written path is the same: gap, boundary, build, keys.

Door 1 · Website

The website plan

Brief by form. Page plan and scope by email. First working draft in five business days. One revision round, launch, and handoff. The fee is named on the plan page.

Get the website plan
Door 2 · Systems

Work still running on memory

A paid diagnostic names the constraint worth fixing first. A bounded pilot is optional and only offered if that diagnostic supports it.

See business systems
Door 3 · Reception

Phone reception

Objections first: will it sound like the shop, does urgent reach a human, can it take two calls at once. The tool is chosen after the rules are written.

See phone reception

Job 03 · Reception

A phone that answers when you can’t

This is a first-class offer, not a footnote under process. No vendor names. The tool is chosen after the rules are written.

  1. 01

    Will it sound like us?

    If callers can tell it is not you, they hang up. Greeting, voice, and facts have to match the shop. A generic receptionist is worse than voicemail.

  2. 02

    Urgent. Who picks up?

    A burst pipe, a no-heat call, a locked-out customer. Those cannot wait in a queue of FAQs. Urgent has to leave the machine and reach a human, on a rule you write.

  3. 03

    Two calls at once?

    The second line is the one that currently dies. Reception that cannot take concurrent calls is still a missed-call problem with extra steps.

See phone reception
Home Homie mobile homepage used as a reception prop
Prop · reception
  1. 01

    Find the gap.

    What changed, what the current system fails to carry, and what decision the next version must make easier. For the website plan this is the written brief. For systems it is the paid diagnostic. For reception it is the three objections owners actually ask.

  2. 02

    Write the boundary.

    Scope, exclusions, price, decision gates, and “done” are agreed before production. Missing inputs pause the clock; they do not compress it. Website-plan numbers stay on the plan page. Systems and custom work are priced in the written scope.

  3. 03

    Build the whole thing.

    Positioning, copy, design, and code; or workflow, rules, integrations, and tests; or greeting, escalation, and concurrent-call rules. One engagement. Set review points. One consolidated round of feedback per gate.

  4. 04

    Walk it and hand over the keys.

    The result is checked against the written acceptance, launched, documented, and left in accounts you control. A 30-day warranty closes or care begins.

Plates

Redacted project scope showing the written boundary before production
Plate · redacted scope
Redacted acceptance checklist showing launch verification items
Plate · acceptance checklist

After launch

Care is finite enough to keep the promise true.

Guardian · $149/month

Automated customer-path checks, domain and TLS monitoring, a monthly integrity review. No content edits.

Managed · $299/month

Guardian plus up to 60 minutes of minor changes a month, human-reviewed. Larger work is quoted.

Care is capped at three clients. No plan includes evenings, weekends, or same-day work.

Start with the change

What became too expensive to leave as it is?