- 11 new patterns dropped across all four work functions: Sales, Support, Operations, and Marketing.
- Every pattern runs at L4 autonomy — it executes end-to-end and surfaces only exceptions for your approval.
- No API keys or developer work required — patterns learn from a single demo or plain-English instruction.
- Self-healing means patterns keep running even when the websites they touch update their layouts.
- Patterns can be stacked — a single trigger can chain a sales follow-up, a CRM update, and a confirmation DM.
- Activation time for most patterns is under 60 minutes including the training session.
What Just Dropped — and Why It Matters
Every few weeks the Koira marketplace adds new automation patterns: pre-built, opinionated workflows that solve a specific recurring problem for owner-operators. Not templates. Not blank canvases. Patterns that already know what to do — you just teach them your version of it once.
This month's drop is the largest single batch since launch: 11 new patterns spanning all four functions of work. Below is the full breakdown, organized by function, with the specific problem each one eliminates.
Sales Patterns (3 New)
1. Dead-Lead Reactivation Cadence
Most CRMs have a graveyard — leads that went cold after the first or second touch and never got a proper follow-up sequence. This pattern identifies contacts that haven't responded in 21+ days, generates a voice-matched reactivation message (based on your previous sent emails), and queues it for approval before sending. It runs the cadence across three touches over seven days, then marks the lead as archived if there's still no response.
Who it's for: Any business running outbound sales where leads fall through after the initial pitch — agencies, consultants, dealerships, and service businesses with longer decision cycles.
2. Inbound Qualification Router
When a new inquiry lands — via contact form, DM, or email — this pattern reads the message, scores it against your defined criteria (budget signals, urgency language, service match), and routes it: hot leads get an immediate personalized reply and a calendar link; warm leads get a nurture message; poor fits get a polite redirect. No manual triage.
Who it's for: Businesses getting more inbound than they can personally qualify in real time — coaches, agencies, home-service companies.
3. Proposal Follow-Up Nudger
After a proposal goes out, most owners follow up once and then feel awkward doing it again. This pattern tracks sent proposals, fires a first follow-up at 48 hours if no reply, a second at five days, and a final check-in at ten days — each message written in your tone, each one slightly different so it doesn't read like a drip sequence. It stops the moment a reply comes in.
Who it's for: Freelancers, agencies, and service businesses where proposals regularly go silent.
Support Patterns (3 New)
4. Review Response Dispatcher
This pattern monitors your Google Business Profile and any connected review platform for new reviews, drafts a response in your voice within two hours of posting, and queues it for one-click approval. One-star reviews get flagged with a suggested private resolution path before the public response goes out.
Who it's for: Any local business where review velocity matters — salons, restaurants, gyms, auto shops.
5. Refund Request Handler
When a customer emails or DMs about a refund, this pattern reads the request, checks your refund policy, determines eligibility, and drafts the appropriate response — approval with next steps, or a denial with an explanation that doesn't sound like a robot wrote it. Edge cases (partial refunds, expired windows, disputed charges) get escalated to your queue with context already attached.
Who it's for: E-commerce stores and subscription businesses where refund requests eat support hours.
6. Repeat-Question FAQ Trainer
This one works differently from the others. It monitors your inbox for 14 days, clusters the questions that appear more than three times, and generates a draft FAQ entry for each one — complete with your answer, written in your voice, ready to add to your site or knowledge base. It then activates auto-replies for those exact question patterns going forward.
Who it's for: Any business whose inbox has a predictable set of questions that never seem to stop coming.
Operations Patterns (3 New)
7. Waitlist-to-Booking Converter
When a cancellation opens up, this pattern checks your waitlist in order, sends an availability notification to the next person in line, and holds the slot for 30 minutes while they respond. If they don't claim it, it moves to the next person automatically. No manual slot-filling, no double-booking risk.
Who it's for: Salons, clinics, studios, and any appointment-based business running a waitlist.
8. Invoice Chase Sequence
Overdue invoices don't chase themselves. This pattern monitors your invoicing tool for unpaid invoices past their due date, fires a polite reminder at day one, a firmer follow-up at day seven, and a final notice with payment link at day fourteen — all written to sound like you sent them personally. Paid invoices cancel the sequence immediately.
Who it's for: Freelancers, agencies, and service businesses that invoice on net terms.
9. Google Business Profile Pulse Updater
Hours, services, and special notices on your GBP drift out of date fast. This pattern checks your GBP weekly against your source-of-truth (your website or a shared doc), flags any discrepancies, and queues the corrections for one-click publishing. Holiday hours get prompted two weeks in advance based on your calendar.
Who it's for: Any local business where GBP accuracy directly affects foot traffic and calls.
Marketing Patterns (2 New)
10. Competitor Content Gap Spotter
This pattern visits a list of competitor URLs you specify, extracts their published topics and recent posts, compares them against your own content index, and surfaces gaps — topics they're covering that you aren't yet. Output is a prioritized list of content opportunities, updated weekly, dropped into a shared doc or your project management tool.
Who it's for: Businesses doing their own content marketing who want a systematic edge without hiring an SEO agency.
11. Social Proof Harvester
Positive reviews, testimonials, and tagged posts are marketing gold — but most businesses never systematically collect them. This pattern monitors your review platforms and social mentions weekly, extracts the best quotes (sorted by specificity and emotional resonance), and compiles them into a ready-to-use asset doc. It also drafts a social post for each strong review, queued for your approval.
Who it's for: Any business that wants to turn customer love into marketing content without doing it manually.
How These Patterns Are Different from Templates
A template gives you a starting structure. You still fill it in, run it manually, and repeat the work next time. A pattern is a running process — it watches, decides, acts, and only surfaces the things that genuinely need your judgment.
Every pattern in the marketplace operates at L4 autonomy: it runs end-to-end and routes exceptions to your approval queue rather than stopping and waiting for you to drive. The goal is that you review outputs in batches — five minutes in the morning, not five hours spread across the day.
And because Koira works on any website your business already touches — without needing an API — these patterns can reach the tools that traditional automation platforms can't. Your invoicing tool, your booking system, your review platform: if you can open it in a browser, a pattern can work with it.
"A pattern is a running process — it watches, decides, acts, and only surfaces the things that genuinely need your judgment."
Stacking Patterns for Compound Automation
Individual patterns are useful. Stacked patterns are where the real leverage lives.
Example stack for a service business:
- Inbound Qualification Router handles new inquiries → hot leads get a calendar link
- Proposal Follow-Up Nudger activates after the proposal goes out
- Dead-Lead Reactivation Cadence catches anyone who went cold after the proposal
- Invoice Chase Sequence fires once the job is done and the invoice is sent
That's the entire sales-to-payment cycle running on autopilot. You show up to close, approve the edge cases, and handle the work itself. The administrative layer runs itself.
What's Coming Next
The next pattern batch (targeting late October) is focused on multi-location operations — inventory sync across physical and digital storefronts, location-specific GBP management, and cross-location staff scheduling confirmations. If you're running more than one location and drowning in coordination overhead, that batch is built for you.
Requests from the community continue to drive the roadmap. The Refund Request Handler and Waitlist-to-Booking Converter both came directly from user requests submitted in the feedback queue. If there's a specific workflow eating your evenings, submit it here — patterns that get multiple votes move to the front of the build queue.
“A pattern is a running process — it watches, decides, acts, and only surfaces the things that genuinely need your judgment.”
| Area | Doing it manually | Running a Koira pattern |
|---|---|---|
| Lead follow-up | Owner remembers to follow up, drafts each message individually, loses track after 2 touches | Pattern fires a 3-touch cadence automatically, stops on reply, routes non-responders to archive |
| Review responses | Reviews sit unanswered for days; owner batches responses once a week when they remember | Pattern drafts a response within 2 hours of posting; owner approves in one click |
| Overdue invoices | Owner sends one awkward reminder, then avoids following up to preserve the relationship | Pattern runs a 3-touch sequence in the owner's voice; stops the moment payment clears |
| Waitlist management | Owner manually calls or texts the next person on the list when a cancellation opens up | Pattern notifies the next person automatically, holds the slot 30 min, moves on if no response |
| Content gap analysis | Owner periodically checks competitor sites by hand, no systematic tracking | Pattern visits competitor URLs weekly and surfaces a prioritized gap list automatically |
| Activation effort | Each workflow requires building from scratch — tools, logic, testing, maintenance | Pattern activates in one training session; self-heals when sites change |
How to activate a new Koira automation pattern without disrupting live workflows
- 01Browse the marketplace and pick one pattern. Go to the Koira marketplace and filter by the work function where you're losing the most time — Sales, Support, Ops, or Marketing. Pick one pattern, not three. Starting with a single pattern lets you calibrate the approval queue before adding volume.
- 02Run the training session. Either walk through the task once on the live website while Koira observes, or describe what you want in plain English in the setup prompt. The pattern maps the workflow from that single session — no configuration files, no field mapping.
- 03Set your approval threshold. Decide which outputs you want to review before they execute and which can run automatically. For a first activation, set everything to 'queue for approval' so you can validate the pattern's judgment against your own for the first week.
- 04Run in parallel for 5 business days. Let the pattern run alongside your existing manual process for five days. Compare its outputs against what you would have done. This surfaces any edge cases the training session didn't cover and builds your confidence before you hand it full autonomy.
- 05Tune edge cases from the queue. Any output the pattern flagged as uncertain will appear in your queue with its reasoning attached. Use these to refine the pattern's logic — either update the instruction or add an example. Most patterns need fewer than three tune-ups before they run cleanly.
- 06Reduce approval gates as confidence builds. Once the pattern has run 20–30 cycles without producing an output you'd change, move routine actions to auto-execute and keep only genuine edge cases in the approval queue. This is the shift from L3 to L4 autonomy in practice.
- 07Stack a second pattern once the first is stable. After the first pattern has run autonomously for two weeks, add the next one. If the two patterns share a workflow (e.g., inbound qualification feeds into proposal follow-up), connect them so the output of one triggers the other, and test the handoff in approval mode first.