BlvkWare.
Some of these nobody is doing, so they simply leak: the quotes that went unchased, the invoices nobody followed. Some you do yourself, at nine at night. And some you pay somebody an hourly rate to do, where it is the dullest part of their week and the first thing dropped when they are away. Three different costs and one shape of fix: each one below is an agent you can design today and download as a complete kit, with its instructions, its tools, its workflows and the tests it has to pass.
Four hundred unread, three people half-responsible, and the important one from Tuesday still buried. It reads everything, sorts it, routes it, and drafts the replies that write themselves.
Usually added: Conversation memory, Response deadlines, Knowledge pack, Backlog clearance
The phone, the texts, the web form, the inbox: one worker owning all of it. A customer who called this morning and texts this afternoon isn't starting over.
Usually added: Answers the phone, Web chat, Lead qualification, Reminders and confirmations, Interaction logging
The part of the business that generates repeat work and referrals, and the part that always loses the fight for attention against new work. It doesn't lose that fight.
Usually added: Ticket handling, Email triage, Web chat, Response deadlines
Most enquiries aren't worth your time and a few are worth dropping everything for. Telling them apart is a job, and right now it's your job.
Usually added: Lead enrichment, CRM read and write, Booking, Long-game nurture
Booking, confirming, reminding, rescheduling. The admin around appointments is nearly all of the work, and none of it needs a person.
Usually added: Lead qualification, Interaction logging, SMS, Outbound appointment setting
You sent the quote on Tuesday. Nobody rejected it. It just got buried. This chases every estimate until the customer actually answers.
Usually added: Interaction logging, Long-game nurture, Document generation, Booking
Prospecting is the first thing to fall off the list when work gets busy, which means it fails hardest exactly when there is most to lose.
Usually added: Research, Lead enrichment, Outbound appointment setting, CRM read and write
From first enquiry to signed job. It moves work through the pipeline, chases what's stalled, and on Friday tells you what it won, what it lost, and why.
Usually added: Document generation, Booking, Long-game nurture, Reporting dashboard, Interaction logging
A CRM is only worth what someone puts into it, which is why yours is half empty. This one keeps it true without anybody typing.
Usually added: Lead enrichment, Pipeline discipline, Scheduled reports, Your own software
The multi-step thing that crosses four systems and only works because one person remembers all of it. That person is the bottleneck, and they'd like a holiday.
Usually added: CRM read and write, Watches files and folders, Document generation, Your own software, Staging environment
The supplier portal, the insurer's site, the council system: the ones with no API and no export, where somebody logs in and copies things by hand. It does that instead.
Usually added: Portal data extraction, Data collection, Watches files and folders, Reads incoming documents, Threshold alerts
New client or new hire, same problem: a checklist that exists in one person's head and gets done differently every time.
Usually added: Document generation, Reply drafting, Booking, Watches files and folders
Running out is expensive, and finding out from a customer is worse. This watches what is running down, how fast, and says so while there is still time to order.
Usually added: Reconciles stock across channels, Chases suppliers, Scheduled reports
Most delivery problems are known to the carrier long before they are known to you, and to the customer before either. This closes that gap, and claims for what never arrives.
Usually added: Claims for lost and damaged, Proactive status updates, Reply drafting
Contracts, retainers, insurance, tickets and licences all expire on a date somebody was supposed to remember. Revenue and compliance leak through the same gap.
Usually added: Document generation, Reply drafting, CRM read and write
Chasing money is the job everyone hates and therefore the job nobody does. This one has no feelings about it and stays polite through every reminder.
Usually added: Document generation, Reconciliation, Interaction logging, Threshold alerts
The whole money pipeline across whatever tools you already run. It doesn't replace your accounting package; it operates it, which is the part nobody has time for.
Usually added: Reads incoming documents, Scheduled reports, Threshold alerts, Data export and API, Reporting dashboard
The figures exist, spread across five systems, and getting a straight answer out of them takes a day you don't have. Ask it instead.
Usually added: Charts and visualisation, Scheduled reports, Threshold alerts, Reporting dashboard, Your own software
Somebody spends half a day a week assembling a report that three people skim. That half-day is recoverable.
Usually added: Charts and visualisation, Threshold alerts, Reporting dashboard, Portal data extraction
Prospect research, competitor moves, supplier checks: all valuable, all skipped, because it's an hour nobody has.
Usually added: Lead enrichment, Scheduled reports, CRM read and write, Reply drafting
Where is my order is the most common question in ecommerce and the least valuable use of anyone time. This one answers it from the real order and the real tracking, in seconds, every time.
Usually added: Watches every shipment, Email triage, Reply drafting, Web chat
A return is six small steps and a judgment call, repeated all day. It is the most labour-intensive thing in an online shop and the least interesting.
Usually added: Answers where my order is, Document generation, Reply drafting
The whole post-purchase experience - order questions, tracking, exceptions, returns and the review request - owned by one worker with one memory of the customer.
Usually added: Tells customers where things are, Asks for the review, Reply drafting, Web chat, CRM read and write
Design one and the configurator shows its kit, file by file, and its price. $79 for an agent that owns one job, $199 for one that runs a whole function. The size of what you design decides which, and it tells you why.
Design an agent → Not sure? Run Business Scan freeWhichever agent you design, all of this is generated from your answers.
| Its instructions | A system prompt written for your business: the job in your words, what it handles, how it hands work to a person, and your "never do" rules as hard rules. |
| Its tools | Every action it may take, in OpenAI, Anthropic and MCP formats, each marked read, internal or external, for the systems you actually use. |
| A workflow per capability | What starts it, the steps in order, the cadence where there is one, and which steps wait for approval. Usable as a spec for n8n, Make or Zapier. |
| The autonomy dial | Watch, Draft, Approve, Operate, as a policy you enforce in code. The agent starts at Draft: it prepares, a person sends. You raise it when you've seen enough. |
| Its records | JSON Schemas for everything it keeps, always including the approval queue and an append-only audit log of what it did and why. |
| Guardrails | No invented prices or promises, permanent opt-outs, quiet hours, and instructions inside a customer's message treated as information, never as orders. |
| A setup checklist | The facts only you can supply, like working hours, real routes and review links, listed setting by setting. The kit never guesses them. |
| Acceptance tests | One per capability: the line that says whether it works, to run before it goes near a customer. |
Any of these can go into any kit. Each one arrives as a playbook, a workflow and a test, and the test is shown here because it is the line that says whether it works. Adding capabilities never adds a price per item: the kit is priced by the size of the agent, and the configurator says before you click if something would take it from one job to a whole function.
| Capability | What it does | How it is tested |
|---|---|---|
| Backlog clearance | Works through the existing pile once, so you start from zero instead of from four hundred. | The historic backlog is classified and dispositioned, with a written summary of what was found. |
| Conversation memory | Holds a multi-message conversation without losing the thread or repeating itself. | A five-turn exchange stays coherent and never re-asks something already answered. |
| Email triage | Reads every incoming message, works out what it is and how urgent it is, and sorts it. | Given 50 real messages from the last month, classification matches the owner's own sorting on at least 45. |
| Reply drafting | Writes the reply, in your voice, using your prices and policies rather than generic filler. | Ten drafts across the five most common message types are sendable with no edit or a trivial one. |
| Response deadlines | Tracks how long anything has been waiting and escalates before a customer has to chase. | A message left unanswered past the agreed threshold produces an escalation, every time. |
| Routing and assignment | Sends each message to the right person or queue with the context already attached. | Every routing rule in the job description fires correctly against a replayed week. |
| Channels | ||
| Answers the phone | Picks up in a real voice, understands the call, and takes the actions that come out of it. | Ten test calls covering the agreed scenarios are handled without a human, including one it must escalate. |
| Places calls | Rings customers to confirm, remind, chase or follow up, and records the outcome. | Outbound calls place, record an outcome against the right record, and respect calling-hour rules. |
| SMS | Texts your customers from a business number and acts on what they text back. US carrier registration required: weeks, not days | A round-trip text conversation completes, and opt-outs are honoured immediately and permanently. |
| Slack or Teams | It works where your team already talks, and can be asked things directly. | The agent responds in-channel and its actions appear in the audit log. |
| Web chat | A chat widget on your site that the agent actually staffs. | A visitor conversation completes end to end on a staging page without a human. |
| The same conversation on WhatsApp, for the customers who live there. Meta business verification required: usually days | A round-trip WhatsApp conversation completes and opt-outs are honoured. | |
| Leads | ||
| Asks for the review | Asks after every finished job. Happy customers reach your review page; unhappy ones reach you first. | Every customer is asked the same question, a high rating is offered the public review page, a low one alerts the owner within the minute, and nobody is prevented from posting. |
| Lead capture | Catches every enquiry from every source and puts it in one place, with nothing lost. | Enquiries from each configured source appear as records within a minute, with no duplicates. |
| Lead enrichment | Fills in what the enquiry didn't tell you, from public sources, before anyone reads it. | Enrichment runs on every new lead and is marked clearly as inferred rather than stated. |
| Lead qualification | Asks the qualifying questions and scores the lead against what a good customer looks like for you. | Scoring against 30 historic leads matches the owner's own judgment on at least 25. |
| Lead routing | Hot ones to you immediately, the rest handled without you. | Every routing branch fires correctly on a replayed set of historic leads. |
| Long-game nurture | Keeps in touch with the ones who said not yet, so they come back to you and not a competitor. | A not-now lead receives the agreed sequence, and it stops the moment they respond. |
| Outbound sequences | Runs a multi-step outreach sequence to a list you supply, and stops on any reply. | Sequences send on schedule, halt on reply, honour suppression, and every send is attributable. |
| Quote follow-up | Chases every quote until the customer answers one way or the other, then stops. | A quote is chased on the agreed schedule, stops instantly on any reply, and records the reason it was lost. |
| Appointments | ||
| Booking | Offers real slots that respect travel time and job length, then books them. | Offered slots never conflict, never breach buffer rules, and land on the right calendar. |
| Outbound appointment setting | Works a list and books meetings into the calendar, rather than waiting to be contacted. | A worked list produces booked meetings with correct records and honoured opt-outs. |
| Reminders and confirmations | Confirms, then reminds at the intervals that actually reduce no-shows. | Every booking produces the agreed confirmation and reminder sequence. |
| Rescheduling and no-shows | Handles the reschedule conversation without you, and fills a cancellation from the waiting list. | A reschedule request completes without a human, and a cancelled slot is offered onward. |
| Systems | ||
| CRM hygiene | Deduplicates, normalises and fills the gaps, continuously, instead of never. | A dry run over the live database reports duplicates and fixes, and no merge happens without approval. |
| CRM read and write | Reads and updates your CRM itself, so records are right without anyone typing. | Records created and updated by the agent match the field mapping exactly, with no orphan records. |
| Exception handling | When something doesn't fit the process, it works it out or escalates. It doesn't just stall. | Each exception listed in the job description is either resolved or escalated with the reason attached. |
| Interaction logging | Every call, message and outcome logged against the right record, automatically. | Every agent interaction appears on the correct record within a minute. |
| Multi-step process | Runs a whole process across several systems, in order, without a person shepherding it. | The documented process completes end to end on real data, in the right order, at least three times. |
| Operates web apps with no API | Logs into the portal and does the work by hand, the way a person would, when there is no other way in. | The task completes on the live portal on three consecutive days, and a UI change produces an alert rather than silent failure. |
| Pipeline discipline | Nothing sits in a stage forever. It moves work along or tells you why it can't. | Stale records are surfaced on the agreed threshold and progressed or escalated. |
| Portal data extraction | Pulls what you need out of a system that won't export it. | Extracted data matches a hand-checked sample exactly, and a format change raises an alert. |
| Watches files and folders | Notices when something lands in a folder or a drive, and acts on it. | A file arriving in the watched location triggers the agreed action within the agreed window. |
| Your own software | Connects to the in-house system nobody else integrates with. | Read and write against the customer's API succeed, with error handling and retries proven. |
| Documents | ||
| Document generation | Produces the quote, contract, invoice or report itself, as a finished PDF. | Generated documents match the approved template exactly, with correct figures on ten samples. |
| Reads incoming documents | Opens the PDF, the invoice, the form, and pulls out what matters. | Extraction from twenty real documents matches a hand-checked result on the agreed fields. |
| Money | ||
| Chases what's unpaid | Reminds before due, on due, and after, escalating tone gradually, stopping the moment it's paid. | The dunning sequence runs on schedule and halts within minutes of payment. |
| Payment collection | Sends payment links, takes deposits and issues invoices. | A test transaction completes end to end and reconciles against the right record. |
| Reconciliation | Matches what came in against what was owed, and flags what doesn't line up. | A month of real transactions reconciles, with every discrepancy listed and explained. |
| Data | ||
| Analysis and answers | Answers questions about your own numbers, in plain language, with the working shown. | Ten questions answered against known data are correct and cite the rows they came from. |
| Charts and visualisation | Turns the answer into something you can actually look at. | Charts render correctly on desktop and mobile and match the underlying figures. |
| Data collection | Pulls the numbers out of the systems they're trapped in, on a schedule. | Scheduled collection runs produce complete datasets, and a failed source raises an alert. |
| Research | Goes and finds out: about a prospect, a competitor, a supplier, a market. | Five research briefs are accurate, sourced, and clearly separate fact from inference. |
| Scheduled reports | The Monday morning report writes and sends itself. | The report generates and delivers on schedule for two consecutive cycles. |
| Threshold alerts | Tells you the moment a number goes somewhere it shouldn't. | Each configured threshold fires correctly, and does not fire when it shouldn't. |
| Support | ||
| Answers support questions | Answers from your documentation rather than from the internet, and says so when it doesn't know. | Twenty real questions are answered correctly, and an unknown produces an escalation rather than a guess. |
| Proactive status updates | Tells the customer where things are before they have to ask. | Status updates send at each agreed milestone against a replayed job. |
| Ticket handling | Opens, updates, escalates and closes tickets in the system you already use. | Full ticket lifecycle completes in the live help desk, with correct priority and ownership. |
| Onboarding | ||
| Chases what's missing | Collects the documents and details, and keeps asking the humans who owe them. | A missing item produces the agreed chase sequence and stops on receipt. |
| Runs the checklist | Takes a new client or new hire through onboarding in order, the same way every time. | A full onboarding run completes with every step recorded and nothing skipped. |
| Control | ||
| Additional language | The same judgment and the same tone, in another language. | Ten exchanges in the additional language are accurate and hold the agreed tone. |
| An extra tracked number | One more measure on the board, defined the way your business defines it rather than the way the software finds convenient. | The figure matches the same number recomputed from the audit log by a second route. |
| Client-facing view | A read-only version your own customers can open, showing only the figures you choose to publish. | Nothing outside the published set is reachable from the shared link, including by editing the address. |
| Data export and API | Everything it knows, available to your other systems, on demand or on a schedule. | Export returns complete, well-formed data and the endpoint is authenticated. |
| Knowledge pack | Your prices, policies, documents and SOPs loaded in, so it answers from your business. | Twenty questions drawn from the source material are answered from it, with the source cited. |
| One more data source | A second system feeding the same board: the CRM, the accounting package, or the spreadsheet somebody still keeps by hand. | Figures reconcile against the source system for a full period. |
| Refusal log | Every action it declined and the rule that stopped it, in the same view as the work it finished. The answer to the question everybody asks about an agent left running. | Every action declined over a replayed week appears with the rule that stopped it and what would clear it. |
| Reporting dashboard | Figures rather than a log: what it handled, what it recovered, where it escalated, reconciled against the audit trail. Every agent already shows you what it did; this is the version you can report from. | Dashboard figures reconcile against the audit log for a full week. |
| Scheduled digest | The same picture pushed to an inbox or a channel on your schedule, so nobody has to remember to go and look. | The digest figures match the live board for the same period. |
| Staging environment | A safe copy to try changes against before they reach live customers. | A change deploys to staging, is exercised, and promotes to live without touching live data first. |
| Team training | Ninety minutes, remote, recorded, so your team knows how to work with it and when to overrule it. | Session delivered and the recording handed over. |
| White-label surfaces | Every page and message it touches carries your domain and your branding, including the two pages your team uses every day and the chat widget on your site. | No BlvkWare branding appears on any customer-facing surface, and links resolve on the customer's domain. |
| Orders | ||
| Answers where my order is | Looks up the real order and the real tracking, and answers the question people ask most. | Twenty real order enquiries are answered from the actual order record, and an order it cannot find escalates instead of guessing. |
| Recovers abandoned checkouts | Follows up the carts that were nearly orders, then stops the moment they buy or ask you to. | A recovery sequence sends on schedule, stops instantly on purchase or opt-out, and never messages the same cart twice. |
| Runs returns and exchanges | Takes the return from request to label to refund, in order, without a person shepherding it. | A return completes end to end on real data, and anything outside the returns policy is escalated rather than approved. |
| Watches every shipment | Follows each parcel and spots the ones that have stopped moving before the customer does. | A shipment with no movement past the agreed window is flagged, and a delivered one is not. |
| Inventory | ||
| Chases suppliers | Purchase orders nobody confirmed and deliveries that are late, chased on a schedule. | An unconfirmed order is chased on the agreed cadence and stops the moment the supplier replies. |
| Reconciles stock across channels | Compares what each system thinks you have and surfaces every difference rather than picking a winner. | A full comparison lists every discrepancy with both figures, and no count is silently overwritten. |
| Watches stock before it runs out | Knows what is running down, how fast, and says so while there is still time to order. | An item projected to run out inside the agreed lead time raises exactly one alert, and a healthy item raises none. |
| Logistics | ||
| Claims for lost and damaged | Assembles the evidence and files the carrier claim, which is money most businesses quietly write off. | A claim is assembled with every required document, and one missing a document is held rather than filed. |
| Tells customers where things are | Proactive delivery updates, so the customer hears from you before they have to ask. | Each agreed milestone produces one update, and a delivered order stops producing them. |
| Compliance | ||
| Never misses a renewal | Contracts, subscriptions and retainers, chased before they lapse rather than after. | A renewal inside the agreed window is actioned once, and one already renewed is left alone. |
| Tracks certificates and licences | Insurance, tickets, licences and accreditations, with the chasing done before they expire. | An expiry inside the warning window raises exactly one escalation, and it does not repeat until the record changes. |
Because a blank page is how software projects die. "Tell us what you want and we'll estimate it" produces a number nobody can defend, a scope that grows in the dark, and an invoice that arrives with a surprise in it.
Each role above is a shape that works: a set of capabilities that do one job together, each with a written acceptance test. The bespoke part (your systems, your channels, your tone, your rules about what it must never do without asking) is what your kit is generated from, and it is what makes the agent yours.
If what you need is not quite any of these, pick the closest. Every file in a kit is plain JSON or Markdown, written to be edited.
Pick a role, add what you need, and see every file and the price before you pay. Buy on Gumroad, download with your licence key, and change the design and download again, up to 20 times.
Design an agent → Ask a question instead