01
Monday
↳ You
You send a Loom.
Screen-record the QQCatalyst task that eats your week. No script, just “every Monday I copy these into QQCatalyst and email the agent.” Don’t know what to record? We have a five-question prompt.
What we build on top of QQCatalystThe QQCatalyst busywork
The QQCatalyst busywork
worth automating.
We read what is already in QQCatalyst and handle the repetitive steps around it. Deterministic where a wrong number matters, AI where it earns its seat, and you approve which is which.
Commercial submissions
We assemble the submission from the QQCatalyst account, run it through the carrier portals, and bring every quote back to the record.
How submission automation worksACORD forms, prefilled
ACORD 125 / 126 / 130 / 140 generated from the QQCatalyst record and rule-checked before they leave: applications ready, not half-blank.
ACORD automation in detailCarrier portals, worked for you
Logins, navigation, and form-fill across each carrier site, entered once from QQCatalyst instead of re-keyed per carrier.
Carrier portal automationRenewals that prep themselves
Upcoming renewals surfaced from QQCatalyst, re-marketed across carriers, and packaged for the producer ahead of expiration.
How renewal remarketing worksQuotes written back
Premiums, quote PDFs, and policy numbers synced into the right QQCatalyst fields. No manual transcription from a portal tab.
How quote sync-back worksWant to feel the data plumbing before you book? A few of these run free, no signup: you can autofill an ACORD from a DOT number, decode a VIN, or browse all the free tools.
Need something deeper than ready-made automation, like a custom integration against QQCatalyst’s own APIs, or an engineer embedded in your team? Insurance engineering and integration services covers the engineering side, and you can hire insurtech engineers who already know QQCatalyst.
And when the missing piece is software rather than a workflow (a client portal, a program rater, a book-roll tool over your QQCatalyst data), see custom insurance software development for agencies: built on your AMS, demoed in week one, yours to keep.
How it actually worksYou record a Loom.
You record a Loom.
We do the rest. Same week.
No statement of work, no change orders, no “out of scope.” A named build lead in your Slack from day one, working inside the QQCatalyst setup you already have.
02
Same day
↳ Your build lead
A real human replies, by name.
Your build lead watches the Loom and replies in your shared Slack with what she heard, what she’d build, the time it saves, and a one-line confirmation: “demo Friday at 10.” The recommendation comes before we build.
03
Friday, 10am
↳ You + your build lead
You watch it run on your real data.
Not a mockup. The actual automation, inside QQCatalyst, running on this morning’s data. We screen-share, you click around, you push it. We keep building until you say “that’s the thing.”
04
Every week after
↳ Us, quietly
It keeps working. We keep watching.
Carriers change portals. APIs deprecate. Your team adds a column. We get the alert before you do. Most of the time you find out something broke only because we Slack you the fix.
What clients actually say
Engineers who already speak insurance.
“It is like having an in-house fractional head of engineering and a fully functional dedicated team.”
Adam Smith
VP of Product · Truckerpath Insurance
“Alfabolt took over our digital platform and internal systems, improved functionality fast, and cut hosting and infrastructure costs by 50%.”
After just a few months, they were a fully integrated part of our team.
Julie Zimmer
CEO · Luckytruck
FAQ
QQCatalyst questions, answered.
Do you work with QQCatalyst?
Yes. We run on top of QQCatalyst and automate the repetitive work around it (commercial submissions, ACORD prep, carrier-portal work, and writing results back), straight from the data already in QQCatalyst. Your team keeps working in QQCatalyst exactly as they do now.
Do we have to change how our team uses QQCatalyst?
No. There is nothing new to learn and no rip-and-replace. We automate the steps that happen around QQCatalyst; your team’s day-to-day inside the system stays the same.
Is this just AI? How do we trust it with a submission?
We use LLMs where they earn their seat: parsing carrier docs, drafting emails. We do not use them where a hallucinated number could send a wrong submission. Your runbook lists what is AI vs. deterministic, and you approve every category.
Does it work across all the carriers we write?
Yes. We automate the actual browser workflow, so it works with any carrier portal your agency uses, with no carrier API access required.
What happens when a carrier changes its portal?
We catch it from monitoring, push a fix, and your run keeps going. Most of the time you find out only because we Slack you that it is handled.
How fast can we get started?
Send a Loom on Monday and you watch it run on your real QQCatalyst data that Friday. Your first automation is live in 14 days. It costs $2,499 once, and only if it is live and your team is using it. After that it is a flat $2,499 a month, month to month. Pause or cancel any time. You keep everything we built.
What does it cost?
It starts free: a 20-minute call and a written automation map of the 3 to 5 workflows worth automating first. Then we build your first automation in 14 days. It costs $2,499 one time. You are charged only if it is live and your team is using it by day 14. If it is not, you pay nothing. After that, the monthly plan is a flat $2,499 a month. The fee does not go up with each workflow, build or carrier. It keeps everything we built running and adds up to 4 new builds a month. $4,499 a month runs two build lanes. Month to month. Pause or cancel any time. You keep everything we built.
The next 20 minutes
Bring the QQCatalyst workflow eating your Mondays.
Leave with a plan.
Twenty minutes, no deck. Show us the QQCatalyst task, we tell you whether we can automate it and what it would cost. If the answer is no, we’ll tell you who can.
Book a consultation →● Limited build slots each month: one build lead per agency