Read a complex technical house, and turn it into a decision.
01
Who it is for
For people drawn to digital strategy, solution architecture, consulting, and company-building more than to living inside code. Understanding code is leverage here — it lets you see technical edges a pure business background cannot — but this is not a developer role. It suits someone who wants to learn how technology becomes a product, a business model, an organisation, and a market, and would rather think across that whole span than specialise in one corner of it.
02
What it trains
- Reading an AI R&E portfolio — the essence-of-form behind its categories
- Structuring a scattered portfolio into a taxonomy and matrix
- Mapping technical assets to business models and commercialisation paths
- Designing a digital / AI-enabled solution for a real workflow
03
Example missions
- Validate Arc's product taxonomy and map the portfolio
- Map business models to Arc's categories and assets
- Research GTM and PMF by product category
- Productise one real business process as a solution-architecture case study
04
What you leave with
- A taxonomy and product matrix
- A business-model × category matrix
- A solution-architecture case study
05
How a mission works
Arc shows you a few real projects it judges you ready for, and you choose the one that draws you. Then it is mission-based and asynchronous — a clear brief in, a concrete artifact out; you investigate, decide, and return with evidence, and Arc evaluates the outcome, not the motion. Expect the start to be hard — unfamiliar tools, an unfamiliar problem space; that crossing is the point.
06
What it is not
- Not a course or a bootcamp — the work is real, and harder
- Not employment, salary, a title, or management — a cultivation path, not a job
- Not a paid role (and no fee either way); not slide decks without substance
07
Selection
- Recognised through real work, by invitation — not an application
- Agency: you move from ambiguity to a usable output without being managed