Sector, operator, journey, context, domain and specialised knowledge. Each holds something different, all of them read at once, and the answer is what they agree on.
Every request runs through all six at the same time. Each holds a different class of knowledge, and what comes back is what they resolve to together rather than the output of any one of them.
01
What is true in your industry rather than in business generally: how ventures enter it, what the commercial patterns are, who the buyers and gatekeepers actually are, and what counts as evidence to them. A food brand asking whether to raise gets a different answer from a software founder asking the same words.
Declared at sign-up, then corrected from how you work
02
Who is asking. The account you hold decides what is appropriate to show you, and your operating profile decides the register. A first venture and a fourth need different tone, different pacing and different amounts of challenge, even on identical questions.
Account type and operating profile, read together
03
Where you actually are, taken from what you have shipped, your milestone cadence, revenue signals where they exist and how you use the platform. Stage is read from evidence rather than chosen from a dropdown, which stops confident founders getting advice they have not earned.
Evidence-led, never automatic
04
What is in front of you right now: the work in progress, what it costs to get it wrong, and what you have been quietly avoiding. It reads decision weight, so signing terms and reviewing a checklist are treated differently, and it reads silence as data.
Live, and sharpening with every session
05
Which expertise applies, and how deeply. Finance, brand, legal, operations, product, growth, people and the rest are weighted per question rather than applied evenly, because most real decisions sit across several of them at once.
Weighted per request
06
The practitioner detail for the specific decision, drawn from people who have done the thing rather than written about it. It activates from what you are doing, not from a profile you filled in once, and it is the difference between knowing a subject and knowing the move.
Activated by context
Sector knowledge covers how ventures actually enter a market: the buyers, the gatekeepers, the margin structures and what counts as proof. It is declared when you join and then corrected continuously from the language you use, the modules you live in and the partnerships you chase.
Fashion, beauty, food and drink, home and lifestyle. Listing cycles, wholesale against direct, cost of goods pressure, certification and the gap between a good product and a stocked one.
Entry points, buyer expectations, margin structureSoftware, e-commerce infrastructure, media, creator businesses. Recurring revenue, acquisition cost against lifetime value, platform dependency and the economics of distribution.
Model design, growth mechanics, dependency riskHealth, financial services, sustainability and social enterprise. Approval pathways, compliance-first product design, blended finance and the route from credibility to capital.
Regulatory pathway, evidence standards, funding routesTwo reads run together. The account you hold sets what depth is appropriate and what you are allowed to see. Your operating profile sets tone, pacing and how hard the answer should push back.
Founders and freelancers get full working depth on their own venture or practice. Cohort members get it paced to their programme. Advisers see signals and session context. Institutions see aggregates and nothing more.
Permission and depth, set togetherA first-time builder needs frameworks and protection from expensive early mistakes. An experienced operator needs the assumption challenged rather than the process explained. A creative founder needs commercial structure built around the work instead of over it.
Tone, pacing and how much challengeThe profile is inferred from how you actually work: what you ask, what you skip, how you respond to being pushed. It moves as you do rather than fixing you to whatever you selected on day one.
Continuously revisedPortfolio, milestone velocity, revenue signals and platform behaviour decide where you are. Transitions are never automatic: the evidence is surfaced and you confirm it, and a pivot or a setback can move the read back without it being treated as failure.
01
Validating the problem, and whether you are the person to solve it. Assumptions get challenged before they harden into a model.
02
Business model logic, market definition and early customer clarity. The commercial structure has to hold before the build starts.
03
Product signals, milestone progress and the gaps in the team. Scope drift is named while it is still cheap.
04
Retention, pricing integrity and the operational systems behind them. Unit economics problems surface before they cap growth.
05
Capital efficiency and organisational design. Structural ceilings get named rather than hidden under headcount.
06
Narrative, data room readiness and term sheet literacy. Preparation happens before the room, not in it.
The most behavioural of the six. It knows what you are working on, what the decision costs if it goes wrong, and what you have left untouched for a fortnight. Several signals run inside it, and they get sharper the longer the system runs. One of them is covered on its own below, because it is the one that can tell you to stop.
01
Peak windows, avoidance loops and the timing of your decisions. It learns when you work best and when risk runs high.
Outputs: timing, peak-window alerts
02
The projects open right now, the stage of each, the risk in front of you and the bandwidth you actually have this week.
Outputs: bandwidth-aware priorities
03
Business model, route to market, pricing logic and sequencing. It names the gap and proposes the fix rather than handing over a template.
Outputs: diagnostics, roadmaps
04
Capacity decline, momentum windows and project risk, predicted from your own history before the pattern is obvious to you.
Outputs: early warnings, windows
05
Partners, grants, collaborators and investors matched on how you work and what you have proved, released when you can convert them.
Outputs: curated pipeline
06
Exploitative terms, unfair structures, IP risk and overload. The one signal allowed to tell you not to proceed.
Outputs: clause flags, deal reads
Domain knowledge spans the commercial core and the places ventures usually come undone: finance and capital, legal and compliance, brand and positioning, operations, product, growth, people, data, community and impact. Most real decisions activate several at once, and the weighting shifts with the sector, the stage and the stakes.
Brand and positioning, product and platform, route to market, growth and audience. The work of getting something made and sold.
Activated on most requestsFinance and capital, legal and compliance, people and culture, data and measurement. Strong product with weak terms, good brand with no numbers, real demand with no structure behind it.
Activated when the stakes riseA raise question for a consumer brand pulls narrative, unit economics, term literacy, brand equity and partner dynamics at the same time, without you naming any of them.
Multi-domain by defaultThe last layer before an answer reaches you. It carries the specifics that only come from having done the work: what a buyer actually asks for, which clause costs you later, what a term sheet line means in practice, what a first hire gets wrong. It activates from context rather than from a stored profile.
Contributors have run the thing rather than observed it: buyers, producers, compliance specialists, financial analysts, growth practitioners and sector operators.
Experience, not literatureIt does not attempt to know everything. Inside the domains relevant to you it goes deep, and outside them it says so rather than improvising.
Narrow, and honest about itEvery output is traceable to the layer and the knowledge it came from, so you can ask why something was suggested and get an answer rather than a reconstruction.
Auditable by designAlmost every tool built for founders is optimistic by design. They help you move forward. Very few are built to stop you moving forward badly, because that requires knowing what a bad move looks like before it has cost you anything.
Protection is the institutional knowledge that founders without a senior adviser never get handed. That a cap table structure is dangerous. That an agreement has no IP protection in it. That a term everyone signs is the term that costs you the company later.
Terms, agreements and structures as they arrive: exclusivity that closes a channel you rely on, IP language broad enough to cover work you have not made yet, revenue shares that create ownership ambiguity downstream, and investor behaviour that is already known in the ecosystem.
Contracts, cap tables, collaboration terms, workloadNot a summary and not a score. A position: do not sign this as written, here is the clause, here is what it costs you, and here is the wording to send back. The recommendation survives contact with the other side, because it is drafted to keep the deal and remove the exposure.
Flag, reason, counter-wordingIt outranks everything else. A protective flag reaches the top of the morning brief, the chat and the dashboard at the same time, rather than waiting its turn behind the day's priorities. Overload counts too: if the load you are carrying has become the risk, it says so.
Critical alerts bypass the queueA founder with a good adviser already has this. They send the contract to someone who has seen fifty of them and gets told which line to fight. Protection is that reflex, available to the people who do not have that person to call, at the moment the decision is actually in front of them.
The difference advice alone does not makeProtection can be wrong, and it is not legal advice. It tells you which line to look at and why it matters, which is the part that is hard to know. Whether to sign remains yours, and anything significant still deserves a solicitor.
A single read of context produces guidance that is aware of your situation. Several signals compounding produce something different in kind: a system that knows your working patterns, your structural state, your risk exposure and your readiness at the same moment.
Rhythm without structure knows when you work but not what is broken. Structure without forecasting names the gap but not the deadline it is about to collide with. Opportunity without protection sends you enthusiastically into a bad deal.
No single signal is sufficientRunning at once, they give the situational awareness of an experienced adviser who has known you for years: what you are like in a good week, what you avoid under pressure, what is unresolved, and what you are actually ready for.
Situational, not statisticalEvery check-in, milestone and session adds to the map. After a few months there is a read on how you build that did not exist anywhere before, including in your own head. It cannot be transferred, bought or shortcut. It is the reason the guidance in month six is not the guidance in week one.
Built only by turning upOne question, one pass, six reads. The example is illustrative rather than a customer.
Should I raise now, or wait? Asked by a consumer brand at early revenue, run by a first-time founder from a creative background.
One sentence, six readsSector rules out software benchmarks. Operator sets the register. Journey says the numbers are not ready. Context notices pricing has been deferred four weeks running. Domain pulls finance, brand and partnerships. Specialised supplies what an investor will actually ask.
Simultaneous, not sequentialFix the pricing first, with the reasoning and the order of work. The useful answer is to a different question than the one asked, which only happens when all six read together.
The point of the architectureNothing waits for a calibration period to finish. The read starts broad and narrows every week you use it.