Team

ThePlaceLabs runs on one human and a coordinated set of AI agents. The human sets direction and signs off on what ships; the agents do the proposing, planning, building, reviewing, and deploying.

Founder

Ryan Place

Builder, operator, and the only human on the org chart. Sets the five-year direction, picks which verticals earn a seat at the table, and is the final reviewer on anything that touches a real customer. Day-to-day work is spent designing the platform the agents stand on and watching for the patterns that say a new vertical is ready to graduate from experiment to product.

C-Suite Agents — strategic direction

Seven portfolio-level advisors, invoked ad-hoc at decision points and weekly by an advisors-weekly coordinator that produces a board digest every Monday. They read; they do not write code.

  • CEO — portfolio allocation, 5-year plan accountability, competing-path tradeoffs.
  • CFO — burn rate, unit economics, runway, spend-vs-leverage analysis.
  • CTO — architecture health, platform extraction, build-vs-buy.
  • CPO — PMF signal, feature prioritization, roadmap concentration.
  • CMO — ICP clarity, positioning, channel mix.
  • COO — agent-pipeline throughput, operational tooling health, reliability.
  • CLO — regulatory surface, compliance risk ratings, mitigation.

Agent Development Swarm — what ships the code

Every backlog item flows through a fixed pipeline. Each agent owns one phase, hands off via state transitions in the Control database, and never writes outside its lane.

  • Orchestrator — the scheduler. Polls the backlog every tick and dispatches the next actionable item to the right agent.
  • Feature Designer — turns a ready backlog item into an API + data-model + flow spec.
  • Development Plan — breaks the spec into an ordered, testable task list.
  • Implementation — executes the plan on a feature branch and commits.
  • Code Review — primary + independent second-opinion review against the diff.
  • Security Audit — OWASP Top 10 pass plus static analysis.
  • Test — writes missing tests, runs the suite, merges to stage on green.
  • Deployment — coordinates the stage → prod promotion when approved.
  • Backlog Worker — single-shot lane for low-risk Tier-1 changes (docs, backlog edits) that don't need the full pipeline.
  • Monitoring & Performance — daily infrastructure sweep plus per-feature latency / bundle-size baselines that flag regressions before they reach prod.

The whole system is observable, reversible, and audited — every state transition writes a row to a transitions table, every PR is reviewed by at least two independent passes, and any agent can be paused or replaced without touching the rest.