Two lanes. One documents a full BA project, end to end. The other fills as the builds land.
A fictional Canadian insurer is drowning in claims intake and wants AI in the workflow. I'm the analyst. Business case, process maps, requirements, prototype, testing, launch — the thinking behind the templates, not just the templates.
Every post I plan to write, in order, with what it's about and why. Read this first.
Read → Stage 01 · DomainP&C insurance basics, what FNOL means, and the questions an analyst asks in week one.
Read → Stage 01 · DomainWhat to ask, who to ask, and how the first answers set every constraint that follows.
Read → Stage 02 · Business caseProblem statement, objectives, and the numbers that make leadership say yes.
Read → Stage 02 · Business caseNaming the assumption nobody wants to say out loud — before it derails the build.
Read →Short, honest write-ups from the founding builds: what was leaking, what fixed it, and what it changed. No theory — receipts.
Field notes only exist when the work does — and the first founding builds are underway. When a business stops losing jobs to missed calls, the story lands here, with the client's permission and their numbers. If you'd like your business to be one of them, the offer page is the door.
If any of this sounds like your business, thirty minutes will tell us both whether I can help.