Scope acceptance
The submitted scope is checked for boundaries, source access, conflict risk, and whether the selected product is enough.
Briefings
Public-source research formats for people who need a bounded evidence view before acting, escalating, buying, or briefing someone else.
Scope review requiredNo public checkout is available.
Briefing enquiries are open for manual scope review. Direct checkout is unavailable. Availability, price, delivery date, terms, and any payment route are confirmed in writing only after scope and capacity review. Sending a scope request does not create an order or guarantee acceptance.
Compare the output formats
Define the decision and evidence depth before requesting review. The final scope and handoff are agreed in writing only if the request is accepted.
| Product | Best for | Depth | Indicative delivery | Handoff | Availability |
|---|---|---|---|---|---|
| Source MapA compact map of entities, public source trails, source quality, and the next questions worth answering. | Fast orientation before deciding whether a topic deserves deeper work. | Single topic / narrow source base | Indicative 2-3 working days after written scope and delivery acceptance | Source map, evidence notes, and next-question list | Manual scope review |
| Decision BriefA structured research brief for a live decision, claim, opportunity, vendor, market, or contested operating question. | A live decision where the useful answer is a bounded judgement, not a data dump. | Defined decision / mixed public-source base | Indicative 4-6 working days after written scope and delivery acceptance | Decision brief, confidence rationale, source appendix, and open questions | Manual scope review |
| Dossier SprintA deeper dossier sprint for power, control, infrastructure, market structure, or source-heavy questions. | Complex source-heavy questions where relationships, leverage, and uncertainty need mapping. | Complex system / broader source base | Indicative 7-10 working days after written scope and delivery acceptance | Dossier, source map, evidence pack, and executive handoff notes | Manual scope review |
Fulfilment protocol
Evidence desk build
Public-source trails are collected, separated by source class, and marked as sourced fact, inference, uncertainty, or open question.
Handoff review
The final product is delivered with clear limits, source appendix, confidence labels, and recommended next checks.
Build a briefing scope
Frame the question, source base, deadline, and exclusions before requesting a manual scope and capacity review.
Before you request scope review
The enquiry path is deliberately simple, and the commercial and fulfilment boundary is explicit.
How do I request a briefing?
Build a scope, then open the prefilled email request. The request is reviewed manually for source access, boundaries, product fit, and capacity. Sending it is an enquiry, not an order.
When are availability, price, and delivery confirmed?
Only in a written reply after scope and capacity review. There is no public checkout at present, and no payment should be requested before the deliverables, price, delivery date, terms, and payment route are agreed.
What if I choose the wrong product?
The builder suggestion is indicative. Manual review may reframe the question, recommend a different output, or decline the request before any order is agreed.
Can I send confidential material?
No. The launch route is for public-source research. Do not send privileged, sensitive personal, medical, legal, financial, or regulated information through the public forms or email route.
Is this advice?
No. Outputs are practical public-source research products with confidence labels, source limits, assumptions, gaps, and next questions. They are not legal, financial, investment, medical, or compliance advice.
What should I prepare before requesting a review?
Use the scope builder, copy the intake pack, keep the scope token, and gather the public starting sources listed in the source starter checklist.