Operate has a five-person public footprint: a CEO and four builders across design and engineering
Asked:“Create an org chart for Operate.so team”
Public-web evidence identifies five current team members at Operate, the CRM startup at operate.so (@operatecrm). No person-to-person reporting lines are publicly stated, so none are invented: dotted connectors below mean “reporting line not publicly confirmed.” Public team-size directories variously indicate 1–10 or six employees, so this chart may be missing one or more people.
Org chart — Moe Amaya at root, four members grouped by function
Dotted line = reporting line not publicly confirmed. Box subtitle = publicly stated title; count = public mentions found. Hover a card to focus it.
Joe Bell, founding design engineer, is the most-evidenced member with 22 public mentions — more than the other four combined.
remaja.twstalker.comDesign is the dominant public function: three of five members (Moe Amaya, Alex Krasikov, Alvish Baldha) sit under design.
sotwe.comClayton K in product engineering is publicly listed only by an abbreviated name, kept as displayed rather than guessed.
w.twstalker.comThe evidence spans three independent hosts and four URLs; no single URL backs more than two of the five rows, and all of it comes from social-profile mirrors because operate.so publishes no team page.
sotwe.com
Evidence table
| Name | Title at Operate | Function | Reports to | Mentions | Source |
|---|
Method: researched org-chart dataset, one row per publicly identified Operate (operate.so) team member — 5 rows, plus a 3-row source-host audit (3 hosts, 4 distinct URLs). “Mentions” counts public mentions of the person’s Operate role found on the source pages. All role evidence comes from public social-profile mirrors; the official site has no team page. Reporting lines are not publicly stated and are drawn dotted, unconfirmed. Directory-listed team size (1–10 or six) suggests possible missing members.