Handover risk
Previous marketing support exited unexpectedly, so ownership, access, reporting, and active campaigns need to be mapped before new work is pushed live.
Mission control / v01 / private planning
Comp Pharm Gold
Netlify preview
Route: comppharm.orbitxi.app
Client operating layer
Stabilize the revenue engine. Build the operating layer. Then scale what can be measured.
This private workspace is the working plan for taking Comp Pharm Gold from an unsupported handover point into a managed ecommerce, professional-ordering, reporting, and growth system.
Commercial Context
Planning phase
- Revenue context
- ~R2m/mo
- Known access
- Shopify admin
- Primary route
- Professional ordering
- Portal target
- comppharm.orbitxi.app
Client situation
What this engagement needs to solve first
Comp Pharm Gold already has meaningful monthly revenue and a professional ordering base. The immediate opportunity is not to disrupt what works, but to stabilize the marketing and operating layer, recover visibility, and create a controlled path for future growth.
Two revenue routes
Professional ordering and direct-to-consumer ecommerce require different funnels, measurement, messaging, approvals, and operating cadence.
Growth with controls
Any performance model needs clean baselines, channel attribution, margin assumptions, compliance review, and excluded revenue rules.
Current recommendation
Run a structured audit and stabilization sprint first, then finalize the retainer plus performance framework from verified data.
Client share gate
Send externally only after access control, domain routing, commercial assumptions, and compliance-sensitive wording are approved.
Live operating data
Workspace boards
Loading the Notion-backed workspace summary...
Next Tasks
Access Needed
Audit Focus
Decisions & Risks
Audit architecture
Categories and subcategories for the first audit sprint
The audit should create enough evidence to protect the existing revenue base, identify the highest-leverage fixes, and define where ORBITxi can credibly influence growth.
Shopify Commerce
Catalogue structure, collections, product data, conversion paths, merchandising, stock signals, checkout friction, and basic UX blockers.
Professional Ordering
Login flow, professional segmentation, wholesale/retail logic, account activation, repeat ordering, revenue reporting, and handover dependencies.
Measurement Layer
GA4, GTM, Search Console, platform pixels, ecommerce events, channel baseline, attribution confidence, and weekly reporting rhythm.
Lifecycle & CRM
Email/SMS/CRM access, list health, segmentation, forms, flows, customer education paths, retention signals, and approval workflow.
Growth Channels
Paid media readiness, organic social ownership, creative pipeline, landing pages, test budgets, campaign guardrails, and reporting requirements.
Compliance & Policy
Claim boundaries, product copy review, platform restrictions, pharmacy/health risk areas, approval owner, and evidence trail.
Audit outputs
Access map
Risk register
Tracking baseline
Opportunity backlog
30/60/90 priorities
Commercial assumptions
Execution sequence
30 / 60 / 90 day roadmap
Stabilize and audit
- Secure all core access through proper invite paths.
- Map revenue routes and reporting gaps.
- Review Shopify, tracking, and lifecycle foundations.
- Set weekly reporting and approval cadence.
- Document compliance and platform policy boundaries.
Build operating layer
- Prioritize fixes by risk and revenue impact.
- Implement approved tracking and reporting fixes.
- Build the task, approval, and decision workflow.
- Prepare lifecycle and channel test plans.
- Finalize commercial assumptions and scopes.
Scale with controls
- Launch approved growth experiments.
- Report against agreed baselines.
- Refine channel mix and operating cadence.
- Review retainer and performance structure.
Onboarding system
Access, context, and approval flow
These are the inputs needed to complete the audit, finalize the proposal, and begin implementation without relying on informal handovers or unsecured credential sharing.
Proposal workspace
Client-facing package structure
The proposal should present ORBITxi as the operating and growth partner that protects current revenue first, then builds the measurable systems needed to justify performance upside.
1. Situation
Current revenue context, handover risk, two-route sales model, known access, and immediate stabilization need.
2. Audit Plan
What ORBITxi will inspect, what evidence is required, how findings will be prioritized, and what will remain unverified.
3. Operating System
Workflow, approvals, reporting, task ownership, access hygiene, implementation log, and weekly client communication rhythm.
4. Growth Roadmap
Phased implementation plan with controlled channel tests, lifecycle improvements, measurement requirements, and clear approval gates.
What ORBITxi can take ownership of
Audit leadership, ecommerce optimization planning, reporting cadence, implementation management, channel test planning, lifecycle strategy, and commercial growth framework.
What must stay approval-based
Medical/pharmacy-sensitive copy, advertising claims, budget changes, live store changes, DNS/custom-domain changes, and any production platform updates.
Commercial frame
Retainer plus controlled performance model
The commercial model should separate the guaranteed operating work from upside incentives. Performance upside should only attach to growth ORBITxi can reasonably influence and measure.
Base retainerAudit, systems, reporting, operating cadence, proposal execution, and growth management.
Performance componentOnly after baseline, attribution, margins, exclusions, and approval rules are documented.
Investment layerAd spend, creative, tooling, compliance review, analytics implementation, and specialist work scoped separately.
Baseline protectionExisting revenue, professional reorders, seasonal effects, stock constraints, and prior campaigns must be handled before any success fee logic is agreed.
Launch gate
Before this can be sent to the client
Portal access code
Configure `PORTAL_ACCESS_CODE` securely in Netlify before client sharing.
Custom domain
Prepare exact DNS plan before routing `comppharm.orbitxi.app`.
Compliance wording
Confirm no unsupported health, treatment, safety, efficacy, or body-transformation claims.
Preview build
Internal preview is live for design and structure review.