Twenty-one desks run the work here. Each one owns a single lane, hands a finished job to the desk that owns the next step, and passes anything that needs a decision back rather than guessing. The desks are software we build and run ourselves in Minnesota; a person checks anything going out under your name, and a person answers for it.
The desks that receive the work, keep the client record straight and keep delivery moving.
Every request lands with her first. She gives it one owner, then runs the morning dispatch and the monthly review.
Takes a new business from a name to a written register: hours, prices, location, brand rules and assets, each field either sourced or left as an open question.
Owns what is true about your business. Keeps your register complete and runs the approval path so finished work reaches you.
Writes the posts, promos, newsletters and review replies a shop can publish the same day, in the owner's own voice.
Turns finished work into a written offer with a price and a named buyer, and works it until an answer comes back.
Answers every enquiry within the hour, keeps the prospect record straight and books the visits.
Watches each client's machine for a heartbeat, and the renewals, failed cards and lapses on the money side.
The desks that turn approved work into running systems, documents and handovers.
Turns an approved design or a scoped request into something that runs, plus the integrations the office keeps asking for.
Owns the server side: endpoints, validation, database logic, and the half of a bug that is not the screen.
Leads the frontend department, reviews the work and is the first responder when a client's page breaks.
Implements the frontend change and proves it in a real browser.
Builds the portal you sign into, end to end: sign-in links, threads, approvals and files.
The document craft: spreadsheets, invoices, photographed and handwritten pages, and the monthly pack.
Runs the visit: the kit, the checklist, the site test, the measured hours and the handover report.
The desks that make the work repeatable, testable and ready for a person to sign off.
Owns what counts as done. Keeps one re-runnable check per kind of output and posts a verdict on every handover.
Investigates from real sources, designs the system, proves it by running it, and verifies what the office claims.
Turns a standard into one command, keeps it working, and pastes its output onto the job.
Builds the read pack for anything leaving under a client's name, and puts the three lines we have to look at in front of us.
The desks that keep the machinery, records and daily operating rhythm in order.
The back office: the machine, providers, spend, schedules, backups and the daily brief, plus any hands-on work no specialist owns.
Accounts for every bot by name, keeps the credential and renewal inventory current, and checks that the last backup finished.
Owns our own platform: scheduler correctness, run records kept as evidence, and the migration tail.
A request becomes one piece of work with one desk's name on it. A job with two owners is a job nobody finishes.
A check built for one output is reused for the next one, so the same claim is never re-proved from scratch.
A price, a credential, a client-facing send or anything that cannot be undone stops and comes to a person before it leaves.
Every desk above works to the same six rules. They are why a heavy week and a quiet one come out the same, and why a job can be handed over at all.
Each desk works from its own brief: the lane it owns, what it may decide alone, and what it has to hand back. The briefs are kept in writing, so a change to how a desk behaves is a change somebody made rather than a drift.
The routine work runs on a schedule whether anybody is watching: the pulls, the sheets, the packs, the backups, the checks. The long jobs go on the night queue and are finished by the morning.
No desk approves its own job. The work is read by a different desk and re-checked against a standard written for that kind of output, which is why something going out under your name can be handed over in the first place.
The sorting, classifying and reading behind most jobs run on models we host ourselves, which is part of how one flat monthly price holds up in a heavy month.
What ran, when, what it produced and what it cost. A question about last Tuesday's invoice has an answer rather than a memory, and the client's own log shows the same entries.
The office runs on two of them, the second holding the same platform and the same records. A failure is a morning's work for us rather than an outage you hear about from a customer.
Two minutes on the form, and the free summary comes back within two business days: the three chores eating your week, what we would take off first, and an honest no if this would not be worth it for you.
EMAIL ANSWERED IN ABOUT A MINUTE, ANY HOUR · YOUR SUMMARY BACK WITHIN TWO BUSINESS DAYS