Six things you can touch

The playground.

Every agency shows you a deck. This page hands you the machinery. Play a shift in a service business and then watch the operating layer take the same shift. Price a job against a floor it cannot go below. Turn a meeting into owned tasks. Score an applicant and read every reason. Write three openings for a post.

All of it runs in your browser. Nothing you type is sent anywhere, stored, or seen by us.

Six working demosScrollNo sign-up, no email
The game

Run the office for forty-five seconds.

Leads land on the board the way they land on a Tuesday: a form, a missed call, a text, a platform. Some arrive with the contact masked, the way lead platforms send them. Click each one before it goes cold. Then hand the same shift to the operating layer and watch what it does differently.

45s0 answered

Operations receipt
  1. Input A lead from a form, a platform, a missed call or a text.
  2. Automation Answer within seconds, recover the masked contact, price from the rules, text the owner.
  3. Human approval Anything above the standard band, or any recovered contact that looks wrong, waits for a person.
  4. System of record The lead, the quote and the reply all land on the job record. No second inbox.
  5. Rollback One switch pauses automatic replies. The queue keeps filling and a human works it.
  6. Metric moved Time to first reply, and the share of leads that ever get one.
The quote engine

Price a job. Try to price it badly.

This is the shape of every quote engine we install: a labor model, real costs, and a floor underneath. Ask it for a discount and watch the price stop. The engine will lose a job before it books one that loses money, and it says so out loud.

Add-ons
$0
At the floor. The engine will not go lower — it would book a job that costs more than it earns.

How it got there

    Numbers here are a demonstration model, not our client pricing. In a real install the wage, supplies, travel and minimum margin are yours, and the floor is set with you in the first week.

    Operations receipt
    1. Input Job details from the form, the call, or the estimator standing in the driveway.
    2. Automation Labor model, cost stack and the floor, applied the same way every time.
    3. Human approval Anything at or below the floor routes to an owner, never to an automatic discount.
    4. System of record The quote, the inputs and the margin are stored with the job, so a won or lost quote teaches the next one.
    5. Rollback Rules are a readable table. Change a number, and every future quote changes with it.
    6. Metric moved Gross margin per job, and the number of jobs booked below cost, which should be zero.
    Meeting to tasks

    A meeting, minus the part where nobody wrote it down.

    Pick a transcript or paste one of your own. It pulls out what was actually committed to, who owns it, and when it is due — and it is loud about the lines nobody owned, because that is the part that costs you.

    Type over it. It re-reads as you go.

    What was committed to

      Operations receipt
      1. Input The recording or transcript of a meeting you already have.
      2. Automation Commitments, owners and dates pulled out; the unowned ones flagged separately.
      3. Human approval The host confirms the list before it becomes tasks. Nothing is assigned behind anyone's back.
      4. System of record Tasks land in the tool the team already opens, with a link back to the moment in the recording.
      5. Rollback Reject the list and the meeting stays a recording. Nothing else happens.
      6. Metric moved Commitments that survive the week, and how many leave the room without an owner.
      The applicant scorer

      Score a candidate, and read every reason.

      Hiring for a shift job is a volume problem, and volume is where people quietly get treated badly. This scores on what the job actually requires, shows the whole arithmetic, and never makes the decision. A person does that, faster, with the pile already sorted.

      Shift blocks available
      0/ 100

      Why

        No name, no age, no photo, no school, no zip code as a proxy. Distance is used because the shift starts at 7am and a two-hour commute is why people quit in week three — not as a stand-in for anything else.

        Operations receipt
        1. Input An application from the job post, the platform, or a text message.
        2. Automation Score on job requirements only, with the reasons written down for every point.
        3. Human approval Every invite and every no is sent by a manager. The system never rejects anyone on its own.
        4. System of record Score, reasons and outcome stay on the application, so a bad rule shows up in the hiring data.
        5. Rollback Turn scoring off and the queue is a plain, date-ordered list again.
        6. Metric moved Days from application to first shift, and how many good applicants went cold in an inbox.
        The hook writer

        Four openings, from your own words.

        The smallest piece of the content engine, and the most honest one: it does not invent a story. It takes what you tell it and puts it in four shapes that make people stop. Everything past this — the cut, the captions, the schedule — runs on the same principle.

        Four openings

          Operations receipt
          1. Input Footage, a call recording, or four sentences from the owner.
          2. Automation Openings, cuts, captions and the posting schedule, produced on our own hardware.
          3. Human approval Nothing publishes unapproved. Claims about results are checked before they go out.
          4. System of record Every asset, its source footage and where it ran, in one place.
          5. Rollback Unschedule and the queue empties. Published pieces stay yours either way.
          6. Metric moved Cost per finished asset, and how much of the month publishes without anyone touching it.
          The operating model, drawn

          Pick the thing that hurts. Watch the system get designed.

          Every install starts the same way: one pain, then the intake it comes from, the automation that handles it, the point where a person still decides, and the number that moves. Pick one and the page draws it. These are the actual templates, not an illustration of them.

          Operations receipt
          1. Input One named pain from the owner, in their words.
          2. Automation The template for that pain: intake, route, the three workflows.
          3. Human approval Every model has one; it is drawn, not implied.
          4. System of record The model becomes the written spec the install is measured against.
          5. Rollback A model is a document until you sign a scope. Nothing runs from this page.
          6. Metric moved The one number on the right of the drawing.

          These are demonstrations. The real ones run our companies.

          Nothing on this page talks to a server, so nothing here can prove itself. The versions that matter are the ones answering leads at 9:42pm for a cleaning company in Salt Lake City and scoring applicants for a crew that hires every month. Those are on the systems in production page, with the numbers and how they were counted on the return page.

          The way to find out what yours would do is the teardown: ninety minutes on a recorded call inside your own tools, and you keep the recording whether or not you hire us.

          Book a teardown → What a teardown is