Market strategy
Combined meeting notes: A3 market entry & monetization strategy
Date: 25 March 2026 (synthesized from 10:14 GMT and 11:48 GMT sessions)
Source document
Market strategy Google Doc — internal working document. Update the wiki when the strategy changes.
Executive summary
Discussions focused on finalising market entry and pricing for A3. The team agreed on an open core hybrid approach to foster developer adoption while driving revenue through scalable cloud infrastructure, specialised add-ons, and enterprise marketplace integrations. Rollout follows a phased Alpha / Beta approach.
1. Open source strategy & product architecture
- Open core model: A3 adopts an open core approach (~80% open source). The core IDE and automation framework stay open source to integrate with the Node.js / npm ecosystem and GitHub.
- Closed source infrastructure: Management, cloud infrastructure (browser runners, monitoring), and specialised metrics dashboards remain closed source to protect IP and drive monetisation.
- Developer acquisition: Target developers directly via social media (primarily X) and evangelism, relying on network effects. The IDE is a downloadable app (similar to Cursor) with no immediate login required.
2. Monetisation & pricing model
- Infrastructure vs. seats: Core revenue comes from compute infrastructure to run automations at scale, not per-seat licensing. High compute needs for web automation yield better margins this way.
- Pricing tiers & mechanics:
- Smart pricing with a monthly minimum (e.g. $20) including baseline usage (e.g. 100 browser hours) to avoid micro-invoicing.
- AI subsidisation: An “AI included” tier to incentivise migration to Automation Cloud; BYOK remains an option for pure open-source users.
- Value-added services: High-margin add-ons include reselling residential proxies (cost ~£0.50/GB, potential sell ~£10/GB) and bot-detection evasions — critical for enterprise users.
3. Enterprise distribution & cloud marketplaces
- Marketplace integration: To reach large enterprise customers (e.g. Skyscanner) who need self-hosting for security or compliance, A3 will list on GCP and AWS marketplaces. Enterprises deploy on their own clouds and pay via existing cloud bills.
- Timeline & costs: Marketplace onboarding is significant effort — estimated 6 months to 2 years, with immediate setup costs around $40k–$50k for Google.
- Trust & reliability: Trust is paramount for large data workloads. Internal enterprise hosting is often cost-prohibitive (dedicated staff), making cloud deployments attractive.
4. Rollout timeline & go-to-market
| Phase | Duration | Focus |
|---|---|---|
| Alpha | 6–8 weeks | Managed testing with trusted users. Usability, runtime issues, core product improvements. |
| Beta | TBD | Broader release; test pricing model (temporarily discounted or waived). |
| Official launch | ~6 months to EOY | Full public availability and marketplace integrations. |
5. Action items & next steps
| Owner | Action |
|---|---|
| Boris Okunskiy | Finalise details with GCP representatives on marketplace kickback model. |
| Marcus Greenwood | Analyse ideal customer profiles (e.g. Skyscanner) and adoption paths. Develop and price automation usage scenarios for target audiences. |
| Team | Initiate onboarding for Google Cloud and AWS marketplaces. |
Related
- A3 Roadmap — 2026 product milestones and delivery plan
- A3 overview — platform and framework context