Marketing for companies that have nobody doing it.
IntellyPilot plans, writes, designs, schedules and reports on marketing for companies where nobody does it. It is our own product: we funded it, we run it, and we pay for every AI request it makes. That last point sounds like an accounting detail. It shaped most of the product.
Not a content-calendar problem. A nobody-owns-this problem.
A small business is not short of ideas for posts. It is short of somebody who owns them. IntellyPilot is built for that gap: it reads the brand once, proposes a plan, drafts the posts and the emails, produces the imagery, schedules everything across the channels the business actually uses, captures the leads that come back and reports afterwards on what worked.
Twenty modules behind one login, including a content studio, a media studio, a calendar, social publishing, email sequences, CRM, leads, reviews, Google Business Profile, competitor tracking and attribution. Fifteen of the publishing channels are separate integrations, each with its own platform approval to clear before a single post can be sent. English and Dutch throughout.
Connecting a language model to a text box is a day’s work. The difficulty arrives a month later, on the invoice.
AI requests cost real money, and the heaviest users cost the most. A flat subscription loses money on exactly the customers you most want to keep. Billing per action leaves the customer unable to predict what they owe, and a blunt usage cap breaks the product at the moment somebody starts getting value from it.
We built the accounting before the features. Every request is measured and converted into credits at a published rate, drawn against a monthly allowance the customer can watch as it moves. Routine work goes to a smaller, cheaper model automatically, because there is no reason to pay a premium rate to decide whether a sentence is a question. And because the credit ledger is ours rather than the payment provider’s, we can make onboarding free without inventing a separate product to do it.
A price we can quote with confidence, and a bill the customer can predict.
Neither is a feature anybody asks for. Both decide whether the business works.| One action | A post, a reply, a plan |
|---|---|
| AI request | Sized to the job: a small model for routine work, a large one where it counts |
| Measured | Priced before billing, at a published rate per thousand tokens |
| Credit balance | A monthly allowance, visible as it moves |
| From outside | Requests arriving through an outside AI assistant are corrected and capped daily, so the same result is not cheaper through someone else’s chat window than through the product itself |
An assistant inside the product, and nothing goes out without approval.
The cheaper option was to expose the platform to outside AI assistants and let customers drive it from whichever one they already use. It costs less to build, and it moves the AI bill onto their subscription instead of ours.
We built the assistant inside the product instead. The customers this platform exists for, a physiotherapist, a gym, an estate agent, are not running an AI assistant of their own and are not about to start. Making that the main way in would have served a technical minority and left out everyone the product was written for. The connector shipped later as well, for the few who want it.
The assistant’s abilities are separated by whether their effects can be undone. Reading and drafting happen immediately: fetch the calendar, look up which posts performed best, write five drafts. The worst outcome is a draft nobody uses.
Anything that reaches the outside world behaves differently. It cannot act at all. It returns a proposal, the interface shows it as a preview, and nothing happens until somebody presses Confirm. Scheduling a week of posts, changing the business profile, cancelling a queue: each returns a proposal rather than a result. That separation is built into what the assistant is able to do, not written down as a policy and hoped for.
From plan to attribution, behind one login.
| Planning | A marketing plan derived from the business itself, with a calendar and a weekly view of what is scheduled |
|---|---|
| Creation | Posts, carousels, advertising creative, email copy and imagery, written in the customer’s own voice rather than a generic one |
| Publishing | Fifteen channels, scheduled and published automatically, with approval before anything goes out |
| Follow-up | Lead capture, CRM with a pipeline, email sequences, review requests and WhatsApp |
| Measurement | Performance by channel and by post, competitor tracking, and attribution from first touch to conversion |
| Knowledge | A document library per workspace that the writing draws on, so answers and copy reflect the customer’s own material |
| Teams | Workspaces, seats, roles and invitations, with approval steps where a business wants them |
| Commercial | A free tier and three paid plans from €39 to €499 per month, each with a monthly AI allowance |
| Compliance | Data export and deletion directly in the product, not by request |
Four review rounds before launch, each deliberately adversarial.
Two of the findings are worth setting out.
A security finding
A platform that assembles imagery has to fetch things on the customer’s behalf: a logo from a web address, a stock backdrop, a linked asset. Each of those is our own system reaching out to an address somebody else supplied. That is a well-known category of vulnerability, and once we counted how many places did it, there were more than we were comfortable with. All outbound requests now pass through a single checked route, and the entry point used by outside assistants was tightened in the same round.
A pricing finding
The pricing page showed dollars. The checkout charged euros. Nobody was overcharged and the payment itself was correct throughout, but for a period we were quoting one currency and billing in another. We corrected the pricing page, then found the same error on every sector landing page.
Of everything in this product, a currency symbol came closest to costing us a customer’s confidence.
The same rounds caught smaller things: free stock imagery drawing down an AI allowance it should never have touched, accessibility gaps in a new screen, and places where a failure could go unreported. All of it found before a customer had to report it.Live, with paying customers, and we are one of them.
| Status | Live at intellypilot.com, with a free tier and three paid plans |
|---|---|
| Ownership | Conceived, funded and operated by Mondivio. No client brief and no investor |
| Why it is here | It is the one system where we are also the customer, and have to live with our own decisions |
Product, build and operations.
Product
- Positioning and pricing model
- Credit model and AI cost control
- Onboarding in four questions
Build
- Twenty modules, fifteen channel integrations
- Assistant with a propose-and-confirm model
- Four review rounds before launch
Operations
- Hosting, monitoring, releases
- Payments via Stripe, billing in euros
- Support and channel approvals
AI for paying customers? The model is the easy part.
What decides whether it works as a business is everything around it: what each request costs, what happens when the allowance runs out, who approves something before it goes out under your name, and whether the bill still makes sense at the end of the month. We have built that once, with our own money.