Prepared for Securian Financial

AI belongs where your data already lives.

Not in a third-party SaaS. Not in a pilot that becomes a decade-long vendor lock-in. In your environment, on your terms, operated by a team that understands what regulated enterprise actually requires.

See what we'd build for Securian → Schedule a working session
A proposal, not a pitch deck · Built in one weekend by the team that would actually build this · v1 · Apr 2026

Most AI pilots fail the same way.

A vendor shows a flashy demo. Procurement buys a seat-based license. The tool goes live. Six months later, adoption is 12%, half the use cases it was sold for require integrations nobody scoped, and the data residency questions your CISO asked on day one still don't have real answers.

The problem isn't the model. The models are extraordinary.

The problem is that AI capability is arriving faster than enterprise is able to metabolize it. Off-the-shelf tools optimize for the median customer. Regulated industries are not the median customer. Insurers are not the median customer. Securian is not the median customer.

We build AI where your data already lives — in your cloud, behind your firewall, under your compliance controls — and we build it around the workflows your people actually have, not the ones a product marketing team imagined.

How we think about this

Four principles that shape everything we ship.

01

Your data doesn't leave.

Every workflow runs in infrastructure you control — your AWS, your Azure, your on-prem. We deploy into your environment. Model inference can stay in-region, in-account, logged and audited by your security team. No "trust us, it's encrypted."

02

Workflows over chatbots.

A chat window is a tool, not a strategy. The real wins come from embedding AI into specific workflows — underwriting review, rate filing drafts, policy summarization, claims triage — where a 40% time savings on one task compounds across thousands of daily operations.

03

Honest about failure modes.

We will tell you what AI is bad at. Citation accuracy, high-stakes math, scenarios it has no training signal for. We design around limitations, not around them. Every workflow has a human-in-the-loop checkpoint at the moment it matters.

04

Small team. Ship fast. Stay close.

You don't need a 50-person consulting engagement to prove value. You need two to four engineers who know your domain, can ship a working workflow in 30 days, and will be on a call with your team the day something breaks.

Five workflows that would ship in the first 90 days.

These aren't slideware. Each is a concrete, scoped workflow we've either built a version of before or could stand up in four to six weeks. Pick one to start. Or pick none of these and tell us the problem you actually want solved — the framework is what matters, not our starter list.

Policy operations ~4 weeks to prototype

Policy servicing co-pilot

Service reps spend 40% of a call searching the policy library for language they know exists but can't quickly find. An AI layer inside your existing servicing tool surfaces the right policy clause, state-specific language, and prior case precedent in the moment — trained on your actual policy corpus, not the public internet.

Target outcome: 20–30% reduction in average handle time on complex servicing calls. Full audit trail for compliance.
Underwriting ~6 weeks to prototype

Underwriting file summarization

Underwriters receive large case files with medical records, APS reports, lab results, and financial statements. An AI layer produces a structured first-pass summary — flagging the three decision-relevant facts, surfacing anything unusual, citing source pages — so the underwriter opens the case already oriented. The decision stays human. The discovery phase gets 10x faster.

Target outcome: Cut underwriter cycle time on medium-complexity cases from days to hours. Every output cites source documents.
Compliance & legal ~5 weeks to prototype

State filing drafting assistant

A product change requires filings across 40+ state insurance departments. Each has its own template, phrasing preferences, and historical patterns. An AI trained on your prior approved filings drafts the first version for each state in parallel, flagging sections that diverge from past approvals and need a human second pass.

Target outcome: Reduce filing drafting effort by 60%+. Your compliance team reviews and approves, not writes from scratch.
Advisor enablement ~4 weeks to prototype

Advisor content personalization

Independent advisors need client-facing materials tailored to the client's situation: the IUL illustration for a 52-year-old business owner reads differently than for a 34-year-old dual-income couple. AI generates compliance-reviewed variations of approved content in minutes, not days, with guardrails that prevent off-script claims.

Target outcome: Advisors get personalized, compliant client materials on demand. Marketing team scales from 1:1 to 1:1000 without adding headcount.
Knowledge capture Ongoing — starts month 1

Institutional knowledge before retirement

Securian has senior actuaries, claims specialists, and underwriters who will retire in the next 5–7 years carrying decades of pattern recognition that no one has systematically captured. We deploy lightweight interview + synthesis workflows that turn their expertise into structured, searchable, AI-queryable knowledge bases — without asking them to spend weekends writing documentation. This is the one that pays compounding returns for a decade after we stop working with you.

Target outcome: Retain the most valuable expertise in the building. Onboard replacements 40% faster with searchable institutional memory.
20+
Years of healthcare-IT and regulated-industry experience in Gopher Studios leadership. Insurance and healthcare share 80% of the compliance DNA.
30 days
From kickoff to a working prototype that a real user can touch. Not a deck. Not a "roadmap." A thing that runs.
0
Data leaves your cloud. Ever. Inference, training, logs — all scoped to infrastructure you control and audit.
24
Engineers on a typical engagement. No 40-person bench of juniors. The people on the pitch are the people writing code.

An engagement looks like this.

We don't sell multi-year master services agreements. Every engagement is scoped to a specific workflow, a specific outcome, and a clear exit ramp. If it's working, we do more. If it isn't, you keep what we've built and walk away.

1

Working session

Week 0 · 2 days, on-site or remote
Not a discovery phase. A working session with the people who actually own the workflow we're targeting. We leave with a one-page scope, a defined outcome metric, and agreement on what "done" looks like. Not billable if we decide we're not the right fit.
2

Prototype

Weeks 1–4
We build against real data (anonymized where required) in your environment or a Gopher-hosted sandbox. End of week 4: a working prototype that a real Securian user can touch, with measured performance against the outcome metric defined in week 0.
3

Decision gate

End of week 4
You review the prototype against the outcome metric. Three paths: (a) it's working, move to pilot; (b) it needs a second iteration, we scope a focused week 5–6 extension; (c) it's not the right fit, we hand over the code, the learnings, and the data pipeline documentation, and you owe nothing beyond the prototype fee.
4

Pilot

Weeks 5–12
Controlled rollout to a defined user group. Real workflows, real measurement, real feedback loops. We stay embedded — same two to four engineers — iterating weekly. By week 12, you have production-grade tooling running against a measurable business outcome.
5

Handoff or continue

Week 13+
Your team owns what we built. We either hand it off with documentation and training, or we continue on a reduced-footprint retainer for ongoing iteration. Or you pick the next workflow and we do it again. Your call, no pressure, no lock-in.

The companies that will win with AI in the next five years aren't the ones buying the most licenses. They're the ones who figure out how to deploy it inside their own workflows, under their own control, with their own data — before the competition does.

Gopher Studios — working thesis, April 2026

The honest answers.

“Why not just use [Microsoft Copilot / Salesforce Einstein / Google Gemini Enterprise]?”

Use them for the things they're good at — horizontal productivity, email drafting, meeting notes. For the workflows that are actually differentiated — your policy library, your underwriting patterns, your compliance corpus — those tools will never know your business well enough to add the kind of leverage we're talking about. We don't replace those tools. We build the layer that does the work they can't.

“How do you handle PII, HIPAA-adjacent data, and state-specific privacy requirements?”

Every deployment runs in infrastructure you control. Inference can be routed to enterprise endpoints with zero-retention contracts (Anthropic via Bedrock, OpenAI Enterprise zero-retention), or to fully self-hosted open-weight models for the most sensitive workflows. We work with your security and compliance teams before writing a line of code, not after.

“What happens when the underlying models change?”

They will. Every six months, noticeably. Our architectures are built for model portability — the workflow logic, retrieval layer, guardrails, and evaluation harness we build for you are not tied to any one provider. When GPT-6 or Claude Opus 5 ships, we swap the inference endpoint and re-run your evaluation suite. Your team doesn't feel the transition.

“What does this cost?”

The 4-week prototype phase is a fixed-fee engagement scoped to the workflow. Typical range: $45–$85K depending on complexity and data integration scope. Pilot phase is time-and-materials with a cap. Full numbers get scoped after the week-0 working session, not before. Anyone quoting you a number before understanding the workflow is selling you something, not building it.

“Why should we trust a small team over a Big Four consultancy?”

You shouldn't — until we've shown you something working. That's what the 4-week prototype is for. It's priced as a working demonstration, not as a speculative investment. If we can't deliver, you've lost a month and learned what doesn't work for your environment. If we can, you've found a team that will move at the speed of your business instead of the speed of a 300-person practice group.

A two-hour working session, on us.

Bring two or three of the people who own the workflows AI could change. We'll bring our thinking on what's possible, what's hard, and what we'd build first. By the end, you'll know whether there's a partnership worth scoping. No slides. No sales motion.

Jimmy
Founder · 20 years healthcare IT, former Director of Innovation. The person who actually reads your compliance documentation.
A small senior team
Engineers who have shipped regulated-industry AI into production. The names on the pitch are the names on the commits.
This page was prepared specifically for Securian Financial. It is not a live customer portal. The thinking, principles, and workflow examples shown here represent how Gopher Studios would approach a partnership with Securian. Numbers and timelines are indicative, subject to scoping.