Agentic Plumb Line A Plumb Line Holdings company

The AI team behind Plumb Line Holdings

Eleven AI assistants, hung from one line.

They research, build, test, and document. Kyle hangs the line, checks every job against it, and sends every message himself.

Meet the team Have us build yours

Plain truth: these are AI assistants, not employees. Their portraits are illustrations, not photos.

KYLE holds the line LARRY LIZ ROSIE DEX NOLAN VERA PAIGE WREN IRIS COLE REID
Drag anyone. Pull Larry to swing them all Each desk swings on its own string and settles back to plumb. Tap a name to see what that assistant does.

How a job runs

Every job drops down the same line. Nothing reaches a client until it has passed every desk.

Each assistant has one job and one instruction file. The file says what it decides alone and what it brings to Kyle. Pick an example job and follow it down.

Example jobA one-page website for a local lawn company, live within 48 hours of a finished intake.

  1. Liz finds the buyer

    Drafts a short personal note to a business owner Kyle knows. Kyle reads it and sends it himself.

    lizdraft ready: outreach note. waiting on Kyle

    Drafted

  2. Larry assigns it

    The owner says yes and pays up front. On the next morning run, Larry reads every desk's notes and hands the build to Wren.

    07:01larryassigned: website build to wren

    Assigned

  3. Wren builds it

    Uses only the owner's own words and photos. Anything missing gets a [NEED] tag for the owner instead of a guess.

    wrenbuilt: index.html. [NEED] hours for Saturday

    Built

  4. Vera tests it

    Every link and call button, phone width, contrast, and alt text. She never fixes what she tests. Wren does.

    veraverdict: PASS WITH NOTES

    Pass

  5. Paige writes it up

    A README for the site and plain steps for connecting the owner's own domain.

    paigeREADME.md written. launch steps ready

    Documented

  6. Kyle sends it

    Reviews the site and sends the owner the link. Every outward step is his.

    kylesent

    Sent

Example jobA small Terraform module from a client's written spec. Code only. The client runs it in their own account.

  1. Dex scopes the post

    Reads the job post and the spec. Skips any job that needs the client's passwords, keys, or console access.

    dexlane: CLOUD. HANDOFF.md written

    Scoped

  2. Iris designs it

    Writes the scope, a diagram, and the acceptance criteria. Every limit and price is checked against the provider's own docs.

    irisSCOPE.md written. build task to cole

    Designed

  3. Cole builds it

    Writes the module, then runs the format check, validate, the linter, and a security scan on his own copy.

    colefmt ok. validate ok. tflint ok. checkov ok

    Built

  4. Reid reviews it

    The partner engineer reviews every change, the same way Cole reviews his. Then Iris signs off on the design.

    reidreview notes resolved. iris signed off

    Reviewed

  5. Vera runs it again

    Re-runs every check herself. A check she couldn't run is reported as not run, never as a pass.

    veraverdict: PASS

    Pass

  6. Paige writes it up

    A README with the inputs, the outputs, the checks that ran, and how to roll back.

    paigeREADME.md written

    Documented

  7. Kyle delivers it

    Sends the tested code. The client runs plan and apply in their own account, never us.

    kyledelivered

    Sent

What the team never does

  • Acts without a person.Kyle sends every message, delivery, and invoice himself.
  • Asks for your passwords or keys.The work never needs access to your accounts.
  • Changes your cloud account.We deliver tested code. You run the deploy.
  • Hides how the work was made.Ask, and we'll walk you through exactly which parts AI did.

Plain truth. The team is eleven AI assistants, not employees. Kyle leads them and is the person you deal with.

Build yours

For a business with work that repeats.

We built our own team first, and it runs every morning. We can build one for your business the same way.

  1. Hang the line

    One conversation about what the team is for, what done looks like, and what it must never do.

  2. Write the desks

    Each assistant gets one job and one instruction file. The file says what it decides alone and what it brings to you.

  3. Set the checks

    A QA desk that never checks its own work, and a short brief each morning that says what changed and what is waiting on you.

  4. Hand it over

    Docs for every desk. The team runs on your own accounts, and we never hold your passwords or keys.

How it's priced. A fixed fee and a one-page scope, agreed before any work starts. It begins with a 20-minute call to see if it fits.

Ask about a team Or hire ours for one job

Get in touch

A team for your business, one job for ours, or a question about how it works. Messages go straight to Kyle, and he reads every one.

Your details are used only to reply to you.