Ian Baer

Simple systems. Real outcomes.

I build and run small, verifiable lead and sales ops systems for insurance — tools you can understand at a glance and fix when they break. Based in Spokane, WA.

What that looks like in practice: a property‑data → CRM import with DNC filtering and run logs; lead‑platform emails parsed into a five‑stage tracker with same‑day outreach prompts; simple contact forms that feed a private inbox and pipeline. Fewer moving parts, tighter feedback loops.

Lead intake automation

Pipeline hygiene

Compliance‑aware workflows

Find me

Email Instagram TikTok X

Services

Property data → CRM import pipeline

Convert property‑data exports into CRM‑ready imports with DNC scrubbing and per‑run logs (input, dropped, callable). Keeps outreach compliant and measurable.

Lead‑platform intake

Parse lead emails into a five‑stage tracker (cold → warm → hot → won/lost), set next actions, and surface same‑day prompts. Focus on policy expiration dates as the key trigger.

Pipeline hygiene + daily due list

Minimal CRM‑lite workflow with clear statuses, due‑today view, and notes that actually get read. Less clutter, more follow‑through.

Simple, compliant forms

Lightweight contact forms that post to a private inbox and your tracker. No publicly shown phone numbers.

Licenses

Property & Casualty insurance

Life insurance

Writing

On small systems

Long‑form note

Small systems win because they make the right behavior the easiest behavior. When a workflow has five steps instead of fifteen, people actually follow it. When the data you need is captured at the moment of action — not asked for later — reporting becomes a by‑product, not a separate project. The point is not minimalism for its own sake; it’s durability. A system you can understand at a glance is a system you can fix when it breaks.

The pattern I use: clarify the single outcome, reduce moving parts, add explicit checks, and write down the boundaries. Everything else can change without breaking the promise. Tools come and go; the system remains legible. That’s how you keep shipping when the ground moves.

Compliance without paralysis

Long‑form note

Compliance becomes paralyzing when it’s treated as a gate at the end instead of constraints at the start. If you make the compliant path the default — the templates, the form fields, the approvals — teams move faster with fewer mistakes. The trick is to encode the rules into the system so less judgment is required at the edge.

In practice: write guardrails as checklists, separate sensitive claims from marketing, and keep an audit trail that’s automatic. You’ll ship more, get fewer surprises, and spend less time arguing about risk because the system already decided most of it.

Get in touch

Quick note — I’ll reply by email. Phone is optional and never shown on the site.