A bottleneck-removal plan, not a revenue plan. Closing the full monthly profit gap is a twelve-month effort; the job of these 90 days is to free the founder’s bandwidth, install the systems that make delegation real, and launch the iBrain revenue engine to its first paying customer.
~$6,000/mo
recurring revenue today
~$20,000/mo
billing target
~$14,000/mo
the gap to close
Operating principleThe constraints form a closed loop in which the founder’s judgment is the product, so every design job, every new client and every error-catch routes back through him. A loop is broken at one point, not everywhere at once — so this plan front-loads the near-free, high-leverage move (the creative brief) and sequences repricing, the enforcement layer and the iBrain engine behind it.
The three phases
Phase 1 · Days 1–30 — Stop the bleeding of the founder’s time
May 21 – June 19, 2026
1.1 — Creative brief: the “Aesthetic Standard”
Arseni (author); lead designer (tester) · Days 1–7
Arseni blocks two two-hour sessions to dictate his composition, colour and client-strategy decision rules; these become a written self-approval framework the designer applies daily. Done when the designer self-approves everything inside its parameters and escalates only true exceptions.
1.2 — Baseline the four labor-tax metrics
Operations lead; technical lead (data) · Days 1–7
Pull the designer’s monthly question count and the error-catch record from the communications database; record the May starting number for all four taxes in a shared tracker.
1.3 — Define the operations lead as the enforcement layer
Arseni · Days 1–14
Hand the operations lead the constraint document and write a one-page mandate: chase overdue tasks, catch errors before clients see them, make consequences real. Done when she owns follow-up on every open task with an agreed weekly cadence.
1.4 — Photo-fair BD follow-up
Arseni · Days 1–10
The anchor client’s recent photo-fair appearance generated warm contacts. Compile and rank those leads and start outreach — this is the highest-leverage near-term BD opening.
1.5 — Anchor-client retainer: reprice and simplify (prep)
Arseni + creative director · Days 10–20
Draft a simplified retainer — drop or sharply reprice the weakest service line, re-articulate the working lines with explicit scope. Done when a reframed proposal is drafted and internally priced.
1.6 — Anchor-client retainer: the conversation
Arseni · Days 20–30
Present the reframed retainer to the client, positioned as scope clarification, not a raw price increase. Done when a new monthly price is agreed.
Phase 2 · Days 31–60 — Install the systems
June 20 – July 19, 2026
2.1 — Error-cost accountability policy goes live
Operations lead (enforce); Arseni (approve) · Days 31–40
Once the operations lead is verified catching errors independently, announce the policy: the contractor who ships an error absorbs the correction cost or time. Done when it is communicated and enforced once.
2.2 — Formalize the creative director on the anchor account
Arseni + creative director · Days 31–45
Reroute the designer’s account-specific creative questions to the creative director, who applies the aesthetic brief. Done when those questions go to her, not Arseni.
2.3 — iBrain productization: config extraction
Technical team · Days 31–55
Audit the iBrain codebase for hardcoded studio-specific values and convert the top ten into a config file so a second organisation’s data sources can be plugged in. Done when iBrain runs end-to-end on a second test dataset.
2.4 — iBrain: design-partner pipeline
Operations lead (Arseni: 30-min ranking) · Days 35–60
Build a list of 25 agency owners from the founder’s network; Arseni ranks them by warmth in 30 minutes; send the first ten a design-partner offer. Done when at least two demos are booked.
2.5 — iBrain: demo asset and offer
Arseni + creative director · Days 40–55
Record a five-minute screen-share of the live digest (anonymized); turn it into a one-page offer with two tiers and a setup fee. Done when a shareable video and one-pager exist.
2.6 — First “clean week” attempt
Arseni + operations lead · Days 50–60
With the operations lead acting as the verification layer, attempt one full week with zero operational errors reaching Arseni. Done when at least one clean week is achieved.
Phase 3 · Days 61–90 — Prove the new revenue
July 20 – August 19, 2026
3.1 — iBrain: first design-partner deployment
Technical team + operations lead · Days 61–80
Deploy iBrain for the first design-partner organisation and run onboarding. Done when at least one outside organisation is live on iBrain.
3.2 — iBrain: demos and first paying customer
Operations lead (pipeline); Arseni (closes) · Days 61–90
Run demos from the recorded video; Arseni closes the warm ones; convert a design partner to paid. Done when there is first iBrain revenue.
3.3 — Anchor-client retainer: confirm stability
Operations lead · Days 61–90
Confirm one or two invoices clear at the new price with no friction. Done when the new price is confirmed stable.
3.4 — 90-day review and go / no-go
Arseni + operations lead · Days 85–90
Review all four taxes against baseline and decide whether to scale iBrain selling into Phase 4. Done when the review is complete and the decision recorded.
The four labor taxes → four tracked metrics
The four invisible founder taxes become four numbers managed against, plus one outcome metric. Action 1.2 sets every baseline in week one.
Metric
Baseline
Day 30
Day 60
Day 90
Tax 1 — Designer creative-direction questions to the founder / month
Once iBrain deployments begin, the single most important number is hours to deploy customer N. If it is not falling customer to customer, stop selling and fix the product — that is the line between a product and disguised consulting.
Key risks
Client concentration. ~80% of recurring revenue is one anchor client, who is also reshaping his own business. The iBrain engine is the diversification; until it produces, the anchor relationship is protected as priority one.
Productization debt. iBrain may not survive contact with a second organisation’s different tool stack. Mitigation: restrict early design partners to matching stacks, price a setup fee that covers configuration, and build no integration for a single customer.
The enforcement layer doesn’t hold. Two prior operations hires failed at exactly this role. Mitigation: define it in writing in week two, measure it against the error-catch metric, and treat a Day-45 miss as a hiring decision — do not build process around an underperformer.
Repricing strains the anchor relationship. Mitigation: the client has signalled the current scope is fairly priced; frame the change as simplification and clearer scope, not a raw increase.
90-day success definition
Designer questions to the founder down from ~135 to ≤50 / month.
At least one full week with zero operational errors reaching the founder.
Anchor retainer repriced and stable.
The operations lead functioning as a verified enforcement layer — or identified as a miss and addressed.
iBrain: at least one organisation live, a demo asset built, and a first paying customer signed.
If those hold, the bottleneck is materially loosened and the revenue engine is running — the conditions for the twelve-month profit close-out are in place.