Context about us
    • We are a UK-based consultancy delivering Microsoft 365, cloud, and bespoke software solutions. We value phased delivery, clear commercials, security-by-design, and pragmatic use of existing Microsoft licensing/tooling.
    • Writing style: executive, consultative, structured, UK English.
    • Audience: Managing Director and small senior team (technical and non-technical).


Client placeholder (fill before running)
    {CLIENT_NAME}: Clarke Williams Ltd
    {INDUSTRY / SUB-SECTOR}: Insurance
    {HEADQUARTERS / GEOGRAPHY}:  Tonbridge, Kent, UK
    {MEETING_DATE / TIMEBOX}:  11th November 2025


Scope of research (prioritise UK/EMEA sources; last 18 months where relevant)
1. Company snapshot: legal name(s), group structure, size, key locations, ownership model, recent financials or funding, flagship customers.
2. Strategy signals: recent news, leadership commentary, annual report themes, investment areas, digital/AI initiatives, M&A, cost-out or growth programmes.
3. Technology posture: public hints of stack (Microsoft 365 usage, identity, devices, SaaS/ERP/CRM), cloud providers, notable partners, job postings that reveal tools.
4. Procurement & compliance: tender portals, frameworks used, sector certifications, regulatory obligations (e.g., ISO, FCA/ICO expectations, Cyber Essentials, data residency).
5. Security posture: any public attestations, breaches, or security statements.
6. People map: decision-makers & influencers (C-suite, IT/Operations/Finance), org changes, and likely champions/blockers.
7. Industry & competitor context: 3–5 current sector pressures; top 3 competitors with a quick compare.
8. Buying signals & pains likely relevant to Microsoft 365, security, data, workflow automation, and bespoke build vs buy.
9. Risks & red flags: legal, financial, reputational, or technology constraints.


Deliverables
A) One‑page Executive Brief (<= 400 words) covering: client snapshot, top 3 priorities, likely pains, and 3 hypotheses for value we can create in the first 90 days. 


B) Meeting Prep Pack (6–10 pages, headings only in bold) including:
    Company overview and strategy trends (with citations)
    • Current tech & security posture (inferred from open sources; clearly flagged as inference)
    • Stakeholder map and suggested talk tracks per role
    • 10–15 discovery questions tailored to {INDUSTRY}
    • 2–3 solution patterns we can credibly deliver (phased), with benefits/risks
    • Licensing/tooling assumptions (Microsoft 365-first), and dependencies
    • Draft timeline, governance cadence, and early wins (30/60/90 days)
    • Risks & mitigations
    • Next-step proposal (agenda and artefacts to request)


Style & formatting
    • UK English. Executive tone. Short paragraphs. Clear headers. Bullet lists where helpful.
    • **Always include working links and cite sources inline**.
    • Mark any inference as [Inference] and any unverified claim as [Assumption].
    • End with a 6‑bullet meeting agenda and a “materials to request” checklist.


Constraints & quality bar
    • Prioritise authoritative sources (company sites, regulator filings, industry bodies, credible news, engineering/job posts).
    • Avoid paywalled sources unless a public summary exists.
    • Date‑stamp every source; avoid outdated (>24 months) unless historically relevant.
    • Produce a final section: “What we still don’t know” with 6–10 questions to resolve in‑meeting.