Agent workflow ownership
Run the GTM agent workflows like a small team: buyer research, city demand, outbound drafts, reply triage, content, analytics, and partner discovery.
Careers
Build the systems behind exact-site world models.
Founding systems leads turn agent runs, city research, capture supply, buyer requests, and delivery work into repeatable operating loops.
Founding GTM Systems Lead
Full-timeRemote, with city-launch travel when useful
Own the human-plus-agent GTM system for Blueprint: city launches, buyer research, outbound, follow-up, content, reporting, and the workflows behind it.
This is for someone who wants to run a lean GTM org where agents do most of the execution. You do not need to be a software engineer. You do need to be unusually good at breaking work into clearly owned workstreams, writing clear briefs, setting review gates, checking outputs, and turning messy market signal into a system the next run can reuse.
Founding Delivery Systems Lead
Full-timeRemote, with site or city travel when useful
Own the delivery system for Blueprint: capture execution, site readiness, hosted-review delivery, buyer success, QA, provenance checks, and the workflows behind it.
This is for someone who can turn messy field and customer requests into repeatable workflows. Agents, contractors, and tools will do much of the execution. Your job is to set the path, check the evidence, catch weak follow-through, and make sure real-site outputs ship without fake readiness or loose provenance.
City launches
Start from zero in a city, use agents to map the market, find robot-team demand, identify capture supply, and leave behind a repeatable launch system.
Delivery loops
Connect capture work, site access, QA, provenance, hosted-review delivery, and buyer success so real-site work does not live in scattered notes.
What You Will Own
The first real GTM system for a lean company.
The work should feel closer to an early Uber city launcher than a conventional growth hire. You will build the process, run it in the real world, measure what happened, and make the next run easier for both agents and humans.
Responsibilities
- Own the GTM system: agent briefs, workstream assignments, QA checks, review gates, dashboards, and weekly operating rhythm.
- Build city-launch playbooks that start with a city and end with named targets, capture opportunities, buyer follow-up, and a clear next experiment.
- Use agents for the heavy work: account research, enrichment, first drafts, market maps, content variants, reply summaries, CRM hygiene, and status reporting.
- Inspect the outputs. Fix weak prompts, unclear owners, stale records, and agent loops that look busy without moving the business.
- Work with the founder on the wedge: exact-site hosted review for robot teams, backed by real capture provenance and buyer-visible proof.
- Use tools like Clay, CRMs, search providers, workflow automation, spreadsheets, LLMs, and Paperclip agents where they help. Keep the system simple enough to understand.
A Normal Week
- Choose one city, define the launch question, and spin up agents to build the first market map.
- Review 40 agent-sourced targets, cut the weak ones, and turn the strong ones into a clean outreach and follow-up queue.
- Rewrite a bad agent brief because the output was too vague, too generic, or not tied to real Blueprint proof.
- Turn buyer replies and objections into new scoring rules, content angles, product notes, and the next agent run.
- Write the weekly readout: what moved, what was noise, where a human needs to step in, and what the system should do next.
Good Fit Signals
- You have run GTM, RevOps, growth, marketplace ops, city launch, founder-led sales support, or scrappy business operations from messy inputs.
- You are fluent with agents. You know how to brief them, constrain them, check them, and make them better without micromanaging every task.
- You are technical enough to use APIs, automation tools, spreadsheets, CRMs, dashboards, and no-code or low-code workflows. You do not need to be a full-time engineer.
- You like field reality: local operators, supply constraints, buyer objections, half-complete data, and small tests that prove what works.
- You care about truth boundaries. You will not call a city live because a deck says so, and you will not let an agent invent a buyer, a site, or a send.
Delivery Systems Lead
Make real-site delivery repeatable before it turns into chaos.
This role sits between capture, site access, hosted review, buyer success, and the agents that keep the work moving. The goal is simple: every messy request should become a clearer workflow, stronger proof, and a cleaner next step.
Responsibilities
- Own the delivery system: capture briefs, site-readiness checks, hosted-review follow-through, QA gates, buyer updates, and proof records.
- Run the delivery agent workflows: capture work, rights and provenance, buyer success, hosted review, field work, site access, QA, and package delivery.
- Turn messy buyer and field requests into repeatable workflows with owners, due dates, acceptance criteria, and clear escalation points.
- Check the hard truth: capture provenance, rights and privacy state, site access, package manifests, hosted-session files, and buyer-visible deliverables.
- Work with GTM and the founder to decide which delivery requests are real opportunities, which are distractions, and what the next run should automate.
- Keep the system boring where it needs to be boring: status, evidence, checklists, and buyer promises should be easy to audit.
A Normal Week
- Take a buyer or site request and turn it into a capture and delivery brief that agents can actually execute.
- Review agent-prepared site readiness, access, QA, and provenance packets before work moves forward.
- Spot the missing proof: a vague capture source, unclear rights state, weak hosted-review record, or buyer update that overclaims.
- Coordinate the human parts of delivery: local capture, site contact, contractor follow-up, buyer check-in, or founder escalation.
- Write the delivery readout: what shipped, what is blocked, what proof exists, and which workflow should become agent-owned next time.
Good Fit Signals
- You have run operations, customer delivery, field programs, implementation, technical account work, marketplace supply, or production workflows.
- You are comfortable managing agents and humans in the same loop. Some work is digital, some work is field reality, and both need clean follow-through.
- You can read a messy request and turn it into a checklist, a runbook, a QA gate, and a buyer-facing update without making it bureaucratic.
- You care about evidence. If package proof, site clearance, or hosted-review evidence is missing, you name the exact gap plainly.
- You are calm around operational mess: late inputs, partial captures, unclear ownership, buyer pressure, and tools that almost work.
Apply
Show us the system you would run.
Send a short note with one workflow, launch, delivery loop, automation, or market buildout you owned end to end. Tell us what the agents or tools did, what you checked yourself, and what changed because of it.