MAKE SENSE × LOVR
Enter password
MAKE SENSE × LOVR
Enter password
You told us the full system made sense but the ongoing monthly did not, not before demand is proven. That was the right read, so this version restructures the offer rather than discounting it. Three changes, plainly stated.
One. The build now covers the complete system and nothing else. Every pipeline, automation, template and journey from the full proposal is in it. No contacts are bundled inside the price.
Two. The monthly drops from $2,400 to $390 and covers only what it costs to keep the system running: the platform, the sending and the support. You run the day to day yourself, which you asked about, and the honest answer is yes, you can.
Three. Contact research becomes its own line at a flat rate per contact. You decide how many, and when, and you can stop and start as demand teaches you. Your database grows at exactly the pace you choose to fund.
And then, your questions. Answered in full after the scope, with the shop priced separately.
$4,900 + GST, one time. Every item delivered, tested and documented inside the fee.
| Deliverable | Qty |
|---|---|
| Positioning and objectives workshop | 1 |
| Ideal client profile, defined per industry | 5 |
| Client journey blueprint, first found to referral | 1 |
| Database architecture: fields, naming, governance | 1 |
| Architecture Document, written and owned by you | 1 |
| Deliverable | Qty |
|---|---|
| Pipelines: Outreach, Enquiries & referrals, Active projects | 3 |
| Pipeline stages, mapped first touch to referral | 21 |
| Custom database fields and tagging rules | 20 / 12 |
| Saved views and filtered lists, including the outreach view | 25 |
| Notification rules, routed by list, stage and source | 8 |
| Deliverable | Qty |
|---|---|
| The outreach view: your list filtered to not yet contacted, strongest fit first, with the reason each business made the list | 1 |
| Template framework per industry: introduction, second note, third note, revival | 20 slots |
| Your copy loaded, formatted and merge fielded into every slot | All |
| Follow up scheduling wired behind each template: one click marks a business contacted, the reminders follow on their own | By design |
| Email authentication on your domain: SPF, DKIM, DMARC | 3 records |
Copy is your craft, so nothing in this build puts words in your mouth. You write the introductions and the follow ups, in your own voice, and we build the structure they live in: the slots, the merge fields, the scheduling, all five industries ready from day one. Wherever your contact research goes, the framework is already waiting for your words.
| Journey | Messages |
|---|---|
| Not yet ready: quarterly notes that keep warm prospects close | 4 |
| Past client: staying present after the project ends | 3 |
| Referral: the considered ask, at the right moment | 2 |
| Nurture messages written and live at launch | 9 |
| Deliverable | Qty |
|---|---|
| Designed proposal template: you fill in the scope and price, send it as a link, and see the moment it is opened and accepted | 1 |
| Booking calendar, synced to your availability | 1 |
| Enquiry acknowledgement from website, Instagram, Facebook, email and Meta lead forms | Under 60 sec |
| Operations messages: proposal reminders, booking confirmation and reminder, invoice reminders, Google review ask, testimonial ask | 9 |
| Core automations live at launch | 19 |
| Deliverable | Qty |
|---|---|
| Website tracking, so every enquiry is traced to its true source | 1 |
| Leads dashboard, live and self serve | 1 |
| Deliverable | Qty |
|---|---|
| Full QA pass: test contacts driven through every journey end to end | 1 |
| Email rendering and deliverability testing | 1 |
| Training session, recorded so you can rewatch it | 1 |
| Written operating documentation, owned by you | 1 |
| Post launch support window | 30 days |
Every journey is walked by a test contact from first enquiry to invoice before a real prospect ever enters it. You see every template and every journey, and approve every word, before anything sends.
You asked about the platform and how much you could manage yourself. Both deserve straight answers. The system is built on an established commercial CRM platform, carried under LOVR's agency licence, in an account that is yours. Every contact, template, pipeline and automation sits inside it, and everything is exportable. If we ever part ways, the database leaves with you.
| After training, day to day | |
|---|---|
| Writing and sending your introductions, from your own address | |
| Marking contacts as contacted and moving cards across the pipeline | |
| Sending proposals, taking bookings, issuing invoices from the templates | |
| Reading the leads dashboard | |
| Ordering contact research batches, whenever you choose |
| Behind the system, every month | |
|---|---|
| The platform subscription, carried in full | |
| Email sending for the automations and journeys | |
| Sender health on your domain: opens, spam placement, reputation | |
| Email support, up to 30 minutes each month |
After the training and the 30 day support window, the day to day genuinely runs without us. The recorded session and the operating documentation exist so you are never dependent on anyone to use your own system.
You have been weighing portals, onboarding platforms and store builders against each other, and the honest answer for a studio your size is that the right setup is smaller than the one you have been shopping for. This is the whole list. One writer, three products, and nothing in here exists to look impressive.
Where people are convinced. The writing, the ethos, the portfolio, the product story, exactly as Lucia has designed it. It is not a system and it should not try to be one.
One place holding every contact, your pipeline, your documents, your invoices, your calendar, your email journeys and your shop. One login. One database. Nothing to connect.
The money underneath both halves of the business. It takes the card on an incense order and the deposit on a writing project. You do not manage it. It runs.
Your books. Xero reads Stripe on its own, so the money arrives in your accounts without anything being built between the two.
The rule we work to is simple. Anything that knows something about a person belongs in the hub. Anything that is a tool rather than a record stays where it is.
| One login, one database | |
|---|---|
| Every contact, incense customer and studio client alike | |
| Enquiries from your website, Instagram, Facebook, email and lead forms | |
| Your pipeline, first enquiry through to referral | |
| Proposal and agreement templates, sent and signed | |
| Invoices, payment reminders and receipts | |
| Your booking calendar | |
| Email journeys for both sides of the business | |
| The shop, its three products and its customer accounts | |
| Subscriptions and loyalty |
| Tools, not records | |
|---|---|
| Your website. Brand, story, portfolio and product pages | |
| Stripe. The card payment on both halves of the business | |
| Xero. Your books, read directly from Stripe | |
| Google Workspace. Your mail and your calendar, connected to the hub |
Every one of those four stays where it is because it is already good at its job and none of them needs to know about the others. The hub is the only thing that needs the full picture, and the only thing we build.
You asked good questions about each of these, so they deserve straight answers rather than a quiet omission.
| Under consideration | Our recommendation |
|---|---|
| A separate onboarding platform | Not needed. It would be a second login, a second subscription and a connection to maintain, doing a job the hub already does for a studio taking on a handful of clients a year. |
| A full commerce platform | Built for hundreds of product lines. You have three. It also charges more before it will tell your database who bought, which is the one thing that cannot be compromised. |
| A customer portal built into the website | No longer possible. The account feature it relied on was withdrawn in January 2026, on existing sites as well as new ones. At three products it would not repay the build even if it had survived. |
| Connectors between platforms | Every connection is a thing that can fail quietly, usually on a weekend, usually noticed on Monday. The fewer joins in a small business, the fewer of those there are. |
At your size the win is not connecting more things together. It is owning fewer things in the first place, and having the one that matters know everything.
You asked whether everything in the Make Sense ecosystem can talk to each other. Most of it does not need to, which is the point of the setup on the previous pages. Here is each one, and what it actually needs.
| You asked about the wider ecosystem | The answer |
|---|---|
| Stripe, for taking payment on proposals, invoices and the shop | Native. Your own account, money to your bank |
| Google Workspace, your calendar and your email | Native. Calendar syncs both ways, mail sends as you |
| Xero, for your books | Xero reads Stripe directly, so nothing needs building between the two |
| A separate onboarding tool such as HubFlo | Possible, and our honest advice is that you do not need one |
There is one connection in this entire setup that we build, and it is the one between your shop and your database. Everything else either already speaks to what it needs to, or has no reason to.
This is worth walking through properly, because it is the piece that makes a separate onboarding tool unnecessary.
Nowhere. We build the template once. Every proposal after that is written by you, sent by you and signed without us ever touching it. You do not send anything to us and you do not wait on anybody.
You asked whether an onboarding platform could issue a new client their account setup the moment a proposal is accepted and the deposit is paid. It could. But both of those moments already happen inside the hub, and anything that happens inside the hub can start a sequence on its own.
An onboarding tool would need to be told all of this by the hub, which already knows it. One system that knows everything beats two systems passing notes to each other, and it is one login instead of two.
The rule is this. A checkout that sits on its own takes card payments and tells your database nothing. The person who just bought RISE disappears the moment the receipt sends, and when you have something worth saying in March you have no way to say it to them. An incense customer and a studio client are the same shape of thing, someone who found Make Sense and liked what they read, and often enough they are the same person.
Your customers earn and the reward arrives on its own. What they will not have is a points balance they can log in and watch, because the account area shows orders rather than a running total. If the range ever grows, that becomes a later addition rather than a rebuild.
| Option | What it gives you | What it costs you |
|---|---|---|
| In the hub Recommended | Checkout, customer accounts, full order history, subscriptions and loyalty. Every buyer in your database automatically, because there is no second system for them to be in. | Nothing extra each month. The storefront is styled to your brand but built in the hub rather than drawn by Lucia, so it will be clean and correct without carrying the craft of her pages. |
| Built into your website | The most beautiful checkout of the three, matching Lucia's design exactly. | No customer accounts and no subscriptions. That feature was withdrawn in January 2026. Loyalty would need a third party tool and buyers would only reach your database through a connection we build and maintain. |
| A commerce platform behind the design | All of it, properly, and the storefront can be made to match. | A monthly platform fee, two paid apps and a higher plan before it will pass buyers to your database. Sized for hundreds of products rather than three, and every future design change becomes a rebuild rather than an edit. |
We keep the two apart on purpose. Your website stays the brand, the writing and the portfolio, exactly as designed. The shop sits on its own branded address that people arrive at once they have decided, which is after the site has already done its work. If the incense range ever outgrows this, the third option is still there, and by then you will have the sales history to know whether it is worth the extra cost.
The point of a setup this small is that you are not tied to anyone to operate it. Here is the line, drawn honestly, including the part where you would need us.
| Delivered, tested and documented | |
|---|---|
| The proposal and agreement template | |
| The storefront, the three products and the postage rules | |
| The customer account area and its emails | |
| Subscriptions and the loyalty counter | |
| Every journey, tag and automation on both sides | |
| Training, recorded, and written documentation |
| No waiting on anyone | |
|---|---|
| Writing and sending proposals | |
| Issuing invoices and taking bookings | |
| Adding a product, changing a photograph, adjusting stock or price | |
| Running a promotion or a discount code | |
| Sending a one off note to your whole list | |
| Reading the dashboard |
A new journey, a template rewritten, a structural change to how the database is organised. Those are ours, and every one of them is quoted before any work begins. Nothing routine sits on our side of the line, which is the whole point of building it this way.
You have social from late September, incense in November and services in January. Nothing here asks you to move any of them.
| When | What happens |
|---|---|
| Late September | The hub goes live and starts capturing. Every enquiry from the website, Instagram, Facebook and email lands in one place from the first day of the social push, so nothing from the launch is lost while the rest is still being built. |
| October | The shop is built while your packaging and product photography are being finalised. Test orders are driven through end to end, including a refund and a subscription cycle, before anything is public. |
| November | Incense launches. Checkout live, customer accounts live, subscriptions available, and every single buyer landing in your database from the first order rather than the hundredth. |
| December | The first repeat purchases arrive, the loyalty counts start reaching their threshold and the incense journey has real people moving through it. |
| January | Studio services launch onto a system that has already been running for three months, with proposals, onboarding, invoicing and the client journey proven rather than theoretical. |
To hold October we need your three products settled: final names, prices, weights and photography, plus what you want the loyalty reward to be. Everything else is ours.
Priced on its own, separate from the Foundation, and entirely optional. Three products keeps this smaller than it would be for a larger range. Around eight working days once your products and photography are settled.
| Included | |
|---|---|
| Storefront designed to your brand, on its own branded address | 1 |
| Three products loaded with imagery, variants, stock, weights and postage rules | 3 |
| Stripe connected to your own account, cards and digital wallets, GST handled | 1 |
| Order, dispatch and delivery emails, written and branded | 3 |
| Customer account area with tracking and full order history | 1 |
| Included | |
|---|---|
| Subscriptions, with welcome, upcoming charge, card failure and cancellation messages | 4 |
| Loyalty counter and the reward, triggered at your threshold | 1 |
| Every purchase creating or updating the contact, tagged incense or both | 1 |
| Incense journey running alongside the studio journey | 1 |
| Live testing: real orders, a refund, a full subscription cycle, account sign in | 1 |
| Shop build, complete | $5,400 + GST |
The shop, the checkout, the customer accounts and the database wiring stand alone at $3,600 + GST, which is everything needed to sell in November and capture every buyer. Subscriptions and loyalty follow at $2,000 + GST whenever you are ready, once the first orders have told you what the reward should be.
Rather than bundling a fixed database into the build and a fixed top up into the monthly, contact research is now priced on its own, at a flat rate, ordered when you want it. This is the part of the system that should scale with demand, so it is now the only part priced by volume.
| Every contact delivered | |
|---|---|
| A business researched against your ideal client profile | |
| The right person at that business: name, role, email | |
| The email verified before it enters your database | |
| Tiered A, B or C for fit, with the reason recorded | |
| Loaded into your outreach view, templates ready |
| Terms | |
|---|---|
| Per researched, verified contact | $1.50 + GST |
| Ordered in batches of 250 | $375 + GST |
| Order by email, any time, any industry | |
| No subscription, no minimum, no expiry | |
| The rate holds as your database grows |
Your concern was funding a fixed monthly before demand is understood. This removes it. When outreach is converting, you order more. When you are at capacity, you order none. The spend follows the demand rather than running ahead of it.
One monthly line, month to month, no term. It carries the platform and keeps the system healthy. There is no research, no content work and no management labour hidden inside it, which is why it is $390 rather than $2,400.
| Included, every month | |
|---|---|
| Platform subscription, carried in full, no licence cost to you | |
| Email sending for automations, journeys and operations messages | |
| Sender health watched on your domain: opens, spam placement, reputation | |
| Email support, up to 30 minutes each month | |
| If you take the shop, its running costs sit inside this same $390. No second monthly line |
Thirty minutes covers the questions a month actually holds. If you ever ask for something larger, a new journey, a template rewrite, a structural change, we quote it before any work is done. You will never receive an invoice you did not see coming.
The Foundation is the same system underneath the full proposal you have already reviewed, so scaling up is a decision, not a rebuild. When demand is proven and you want the running of it taken off your hands, either layer switches on over what is already built. Nothing is redone and nothing you have paid for is repeated.
| When you switch it on | |
|---|---|
| Researched contacts added and tiered monthly, without ordering | up to 500 |
| Templates refined each month on what real replies teach | |
| Follow up cadence kept honest: tasks scheduled, stale conversations flagged | |
| Nurture journeys maintained and seasonal notes written | |
| Monthly report and a quarterly review call |
| When you say go | |
|---|---|
| Campaign and audience strategy, built from your database | |
| Ad creative and copy, directed and produced | |
| Campaign build, management and budget allocation | |
| Conversion tracking wired into the same pipeline, source stamped | |
| Testing, refinement and plain language reporting |
Ad spend is paid by Make Sense directly to the platforms and is separate from this fee. Both layers are priced here so there are no surprises later, not because either is expected soon.
All figures exclude GST. Every line sits on its own: the build is once, the monthly keeps the system on, the contacts are entirely at your pace, and the shop is a separate decision you can make now, later, or not at all.
| What you own | Owner |
|---|---|
| The platform account and every contact in it | Make Sense |
| The client database, with full export rights | Make Sense |
| Every template, journey and line of copy | Make Sense |
| All pipelines, automations and templates | Make Sense |
| The Architecture Document and operating guide | Make Sense |
| LOVR's access | Revocable |
The system is yours from day one and the monthly is month to month. If it stops paying for itself, you stop. We would rather earn the next month than enforce it.
If this structure works for you, reply and we will get the build underway. If any line deserves more explanation, ask. Every question gets a straight answer, this page is built on them.