# OperatorIQ OperatorIQ builds AI system blueprints for B2B founders and solo operators. The premise: instead of working longer, you install a system that runs while you do not. Each blueprint is a pre-built agentic workflow you configure once on a Saturday and run on a schedule from Monday forward. The two live products cover outbound sales and business visibility. A third blueprint covering Obsidian-based knowledge management is in development. The brand is operated by Christine Johnson. --- ## Products ### Agentic AI Sales Blueprint — $97 one-time URL: https://buy.stripe.com/6oU7sMdU99x2f0N7Fybwk0j Nine coordinated agents that handle daily prospect research, cold-email drafting in your voice, five-step follow-up cadence, CRM hygiene, and reply triage. Nothing sends without your approval. 20-minute setup on a Saturday morning. The system then runs on a schedule. What it does: daily ICP-prioritized prospect list with research attached; cold-email drafts written in your voice queued for one-click review; CRM hygiene running in the background (activity, stage updates, follow-up tasks); reply triage with drafted responses ready before you open the inbox; approval gate at every send, nothing fires until you say yes. Tools: Apollo.io (lead discovery), HubSpot CRM (source of truth), Claude Cowork (AI workflow platform). 9 prewired agents, 6 reusable skills, 20-minute setup, yours permanently. ### Agentic AI Live Dashboard Blueprint — $97 one-time URL: https://buy.stripe.com/4gM9AU7vL9x22e1bVObwk0i 20-page implementation PDF, 8 hub-tab templates, 7 reusable build patterns. First dashboard live the same day. Self-refreshing artifacts that pull live data on every open instead of storing stale numbers that require manual maintenance. Eight hub views: pipeline, project, customer health, weekly metrics, hiring, support, content, finance. Pick one, it is live the same day. Live connector reads on every open. Built-in maintenance cadence. Dashboards live in your markdown files, not someone else's schema. ### Bundle — Sales + Live Dashboard — $147 one-time URL: https://buy.stripe.com/6oU14o7vLcJeaKxf80bwk0h Saves $47 versus buying separately. Both flagship blueprints in one purchase. --- ## Writing ### The Agentic Operations System: how it works URL: https://operatoriq.io/blog/agentic-operations-system/ Published: May 6, 2026 Category: AI + Tooling The four-component architecture behind every OperatorIQ blueprint: knowledge base, agent layer, approval gate, connector set. What agentic AI operations actually means for a solo service business — not the breathless version and not the dismissive version. The minimum viable build that starts with one agent and one workflow. The four components: (1) Knowledge base — six short files that every agent reads from: ICP definition, voice and tone, the offer, the sequence, prohibited language, scheduling preferences. (2) Agent layer — narrow agents each owning one workflow, not a general-purpose assistant. (3) Approval gate — every output that touches a live person routes to a review queue before it ships. Not optional during ramp. (4) Connector set — integrations to your CRM, email API, calendar, billing tool. Live reads, live writes. The Saturday Setup Method: the structured prompt sequence that initializes the knowledge base, confirms connectors, runs the first agent in supervised test, and produces a first-week operating schedule. From zero to operational in one Saturday, 4 to 6 hours. The minimum viable build: one agent (follow-up), three knowledge base files (voice, prohibited language, offer), one connector (email), one approval queue. Three hours to set up. Over 90 days, the difference between 30% follow-up coverage and 90%. --- ### The five-job problem: why solo founders run out of hours before they run out of money URL: https://operatoriq.io/blog/five-job-problem/ Published: May 6, 2026 Category: Founder Chaos It is 9:47pm on a Tuesday. You are inside the CRM, fixing a deal stage that has been wrong for two weeks because nobody else was going to fix it. Your dinner is cold on the desk. The proposal you owed a prospect on Friday is still half-written in another tab. Tomorrow's first call is in eleven hours and you have not looked at the deck. This is not a bad week. This is the third week in a row that has looked exactly like this. The business is growing. You are not. That is not a discipline problem. That is the math. A solo founder with real revenue is running five org charts at once: Sales, Operations, Delivery, Marketing, Finance. Each job being done at about 40% of what a competent full-time hire would do. Five jobs at 40% is not 200% of a job. It is 200% of your week, with 60% of the output of one good team. The AI tooling stack to replace those functions end to end runs $200 to $800 a month. The reason it does not feel that cheap when you try it is that you have been buying tools, not delegating jobs. The five-step playbook to take a job back: 1. Audit which job is bleeding the most hours using the Sunday test. Open your calendar and task list and write down what work you actually did on the last three Sundays. 2. Pick the job that runs on a schedule, not the one that runs on events. Schedule-driven work (sales follow-up on day 3, day 7, day 14) is the right first pick because the trigger is a clock, not a person. 3. Build the knowledge base before you build the agents. Write six short files: ICP, voice, offer, sequence, objections, wins. Half a Saturday, $0. 4. Pick one workflow inside the job, not the whole job. One input, one output, one trigger. $20 to $80 a month in tooling. Two to six hours a week returned per workflow, immediately. 5. Set the human-in-the-loop checkpoint deliberately. For the first thirty days, every output goes through you before it ships. After thirty days, the outputs you approved without changing go fully autonomous. That sequence takes one job off your plate inside a month. Inside a quarter you have two systems running on a clock and you are inside the CRM by choice, not by emergency. --- ### Your CRM has 400 contacts and zero open tasks. That is not a pipeline. URL: https://operatoriq.io/blog/crm-with-zero-tasks/ Published: April 29, 2026 Category: CRM Open your CRM. Look at the contacts count. Now look at the open tasks count. If the first number is in the hundreds and the second number is zero, you do not have a pipeline. You have a contact museum. This is an architecture problem, not a discipline problem. Every modern CRM was built assuming a sales team will use it. The defaults encode the same assumption: there is a sales manager, an SDR, an AE, and an ops person. You are all four of those people, which means the protocol is overhead with no payoff. The cost of a broken CRM: a solo founder with $80k of pipeline moving through their CRM in a quarter loses 20% to 40% of it because follow-up never fires. That is $16k to $32k per quarter, or $64k to $128k annualized of revenue that should have closed and did not. The Saturday rebuild. Five steps: 1. Archive the noise. Every contact you have not had a real interaction with in the last 90 days moves to Cold Archive. Not deleted. If you have 412 contacts and only 38 have a touch in the last quarter, your real pipeline is 38. 2. Define five pipeline stages by what changes about your work. New (you just met them), Qualified (you have confirmed fit), Proposal Out (ball is in their court), Verbal Yes (they said yes), Won. Five stages max. 3. Define six fields per contact and delete the rest. First Name, Company, Last Touch (date), Last Touch Type (call/email/DM/in-person), Next Step (free text, what YOU need to do next), Next Step Date. 4. Build the one automation that creates the tasks you would never remember. In HubSpot, build a single workflow: when a deal's stage changes, create a task assigned to you, due five business days from today, with the title set to whatever is in the Next Step field. 5. Run the Saturday triage prompt. Open Claude. Paste your active deal list, the five stages, the six fields. Ask it to confirm stage assignments, draft a one-sentence Next Step for each deal, suggest Next Step Dates, and propose a default follow-up cadence per stage. A CRM you open because there is a task waiting is a pipeline. A CRM you open because you feel guilty is a museum. --- ### The $60k SDR you cannot afford and the $97 system that does the same job URL: https://operatoriq.io/blog/sdr-you-cannot-afford/ Published: April 22, 2026 Category: Sales Workflow An SDR you would hire this quarter costs $60,000 in base salary, plus 22% in benefits, plus a 3-month ramp where they book nothing. Add tooling (Apollo, a sequencer, Sales Navigator) and you are at roughly $90,000 to $120,000 fully loaded in year one. The same workflow, run by a 9-agent stack you can ship in a weekend, costs about $200 a month. The SDR job broken down: open a list of target accounts, research each one, draft a personalized first-touch email, send it, schedule five follow-ups across email and other channels over the next eighteen days, log every touch in the CRM, watch for replies, qualify replies against ICP, book discovery calls. Every line is a workflow. Every workflow runs cleanly inside a current AI agent. Year-one cost comparison: - SDR: $90,000 to $120,000 fully loaded, 3-month ramp, 30% attrition risk - AI system: $200 to $800 per month ($2,400 to $9,600 per year), weekend ramp, zero attrition The six-step playbook to replace the SDR job: 1. Define what the SDR would have done. Write the day-90 daily list out loud: target account research, first-touch drafting, follow-up cadence, CRM logging, reply qualification, discovery scheduling. 2. Pick the one workflow with the highest leverage and start there. For most solo founders this is consistent follow-up after the first touch. It is where deals quietly die today. 3. Build the knowledge base before the agents. Six files: ICP definition, voice and tone with examples, the offer, the sequence with subject lines and timing, prohibited language, scheduling preferences. 4. Set up the tool stack: Apollo, Claude, your CRM. Three tools, maybe four. That is the entire system. 5. Define the human-in-the-loop checkpoint. For the first 30 days, approve every send. After 30 days, audit: every message you approved without changing goes fully autonomous. 6. Set the success metric. Not messages sent. Not open rates. The metric is conversations started per week. Two to four real replies per week within 30 days means the system is working. The first hire that pencils is the one you make after the system has been running for six months, not before. When you do hire, you are hiring someone to close, not to prospect. --- ### If you cannot see your pipeline, you cannot trust it. The dashboard problem solo founders never solve. URL: https://operatoriq.io/blog/pipeline-dashboard-problem/ Published: April 15, 2026 Category: Scaling Ops Open the Google Sheet labeled "Pipeline". Look at the dates in column C. The freshest number is from three weeks ago. The deal in row 14 closed in February and you forgot to mark it. That is not a dashboard. That is an archive of what you used to believe was true. The dashboard graveyard pattern: Google Sheet (six weeks of use, formula breaks, "Pipeline v2" tab started, sheet abandoned). Notion database (two weeks of hand-entry, one deadline, now a snapshot of February). Looker Studio (connected to CSV exports, connector expired after 90 days, now displays a blank state with a grey error icon). Every solo founder has a version of this. The pattern is not laziness. The pattern is that dashboards demand a maintenance loop the solo founder cannot run alongside delivery. The cost of the missing dashboard: a solo founder running $300k revenue who cannot see their pipeline accurately is making forecasting errors of 25 to 40 percent. Two failure modes: declining opportunities you should accept (you feel busy, you are not) and accepting opportunities you should decline (you feel thin, you are already booked through the quarter). Why every conventional fix fails: - Over-built spreadsheet: maintenance cost rises with tab count. Past six tabs, cost exceeds value. - Notion database: data entered by hand. You will not remember to update it. The database becomes a museum of last month. - BI tools: designed for teams, assume a data warehouse and an analyst. You moved the maintenance cost, did not eliminate it. The actual answer: the dashboard does not store data. The dashboard pulls data. Every time you open it, it hits your CRM, billing system, calendar, email API. Call it an artifact. The dashboard is a place you store numbers. The artifact is a place that fetches numbers when you look at it. The Saturday playbook to build your first artifact: 1. Inventory the decisions you need to make weekly. Not metrics. Decisions. Four decisions max. Mine: should I take on the new client, do I need to push outbound this week, am I cash-positive next month, is any active project off-track. 2. For each decision, name the data source. Two sources per decision is the cap. Eight connector calls total. 3. Build the artifact. One panel per decision. Each panel calls one or two connectors when you open it. No data is stored anywhere. 4. Set the refresh logic. Live means on every open. Cache the read for 5 to 10 minutes if connectors are slow. Data should never be more than 10 minutes stale. 5. Set the maintenance cadence. Daily: 60-second read. Weekly: check whether connector schemas changed. Monthly: retire panels you did not open. Quarterly: add new panels for new decisions. Annual: re-architect if the business changed shape. The reason this works and the previous attempts did not: you are not pushing data into a dashboard. The dashboard is pulling data from sources you already maintain because you have to maintain them anyway. --- ## Newsletter ### The OperatorIQ Brief URL: https://operatoriq.io/brief/ Substack: https://operatoriq.substack.com One free essay every Wednesday. No upsells in the body. Unsubscribe in one click. Free tier: one long essay every Wednesday. Paid tier ($9/month): free essay plus one tactical prompt pack from the blueprints every Saturday. Full archive. Founding tier ($144/year): paid tier plus 25% off any blueprint, any time, never expires. Topics: AI systems for B2B founders, CRM architecture, sales workflow, scaling without hiring, agentic operations. Written by Christine Johnson, operator and builder of the OperatorIQ blueprint series. --- ## About Christine Johnson is the operator behind OperatorIQ. She builds agentic AI systems for B2B founders and solo operators who are running every function of their business without a team. The core argument behind OperatorIQ: a solo founder running a real business is filling five organizational roles simultaneously (Sales, Operations, Delivery, Marketing, Finance), each at roughly 40% of what a competent full-time hire would contribute. The answer is not more tools and not more hours. The answer is delegation of entire jobs to systems that run on a schedule. The blueprint series codifies the architecture she uses herself: agent layer, approval gate, knowledge base, connectors. Each blueprint is designed for a 20-minute Saturday setup and runs from Monday forward with minimal intervention. Named frameworks from OperatorIQ: - The Agentic Operations System: four-component architecture (knowledge base, agent layer, approval gate, connector set) underlying each blueprint - The Saturday Setup Method: the 20-minute configuration conversation that initializes the system - The Queue-First Business: the outcome state (you walk into a prioritized queue on Monday morning, not a blank screen) Contact: hello@operatoriq.io Site: https://operatoriq.io Newsletter: https://operatoriq.substack.com