None of the three below depends on the platform decision. They hold whether you stay on WordPress or move to Shopify, which means work on them is not at risk either way. Two of the three need a conversation before they need a number, so what follows is deliberately a set of suggestions and questions rather than an estimate.
One
Klaviyo
Already in your estimate
You are already paying for Klaviyo and using a fraction of what it does. Time to make more of it is included in the proposals you already have, so this is context rather than a new cost. It is also the piece that turns a repaired signup path into orders.
What we would do
- Connect it directly. Your approvals currently reach Klaviyo through a second tool. A direct connection carries more customer and order detail, and removes a dependency that nobody supports.
- Clean the list before sending anything. Your site holds 7,802 registered accounts against roughly 100 that buy. Sending to a list that large and that inactive is how a sending address stops reaching inboxes, and delivery is already a known problem for you.
- Build the sequence from application to first order. Application received, approved, welcomed, first order placed. This is where new professionals are being lost today, and it is the natural companion to repairing the registration path.
- Add a flow for accounts going quiet, triggered by each account's own ordering rhythm rather than a fixed number of days. The same prompt you would otherwise need someone to notice.
What we need to know
- Who has been sending from Klaviyo, and when did it last go out?
- Is the list built from customers, or from everyone who ever registered?
- What record of consent exists for the people on it?
- What do you send today that you would want kept?
Two
A customer system
Suggestion: Zoho Bigin
Zoho Bigin is small, inexpensive, and built for teams of your size rather than scaled down from something enterprise. Standing one up is quick. What takes thought is the data that goes into it and how closely it matches the way you already work.
What it would do, and where the work is
- Hold what currently lives in one person's memory. Who was spoken to, what was discussed, what was promised, what happens next. Twenty accounts carry more than half your revenue and none of that history is written down anywhere.
- Setting it up is the quick part. Account, users, fields and permissions are days, not weeks. Nobody should be quoted a long project for that alone.
- Bringing your data across is the real work. You have 7,802 registered accounts against roughly 100 that buy, company names on some, licenses on about half, and history sitting outside the website entirely. Deciding what moves, in what condition, is most of the effort and most of the value.
- Connecting it to what you already run. Bigin connects natively to Shopify and through a plugin on WordPress, so new accounts and orders arrive without retyping. Klaviyo, your accounting, and inbound email can feed it too. Which of those are worth wiring is a decision rather than a default.
- Shaping it around your process. The stages an account moves through, what raises a task, and what someone sees when they open it in the morning. This is the difference between a system that gets used and one that gets abandoned, and it is where we would spend the time.
- Cost is modest, in the range of $7 to $9 per user each month, billed by you directly.
What we need to know
- What should come across: every registered account, buyers only, or a cleaned subset?
- Where does account history live today that is not on the website? Email, notes, spreadsheets, memory?
- In your own words, what happens between a professional first making contact and ordering regularly?
- Which systems should feed it: store orders, Klaviyo, accounting, inbound email?
- What would someone need to see when they open it each morning?
- Who would use it daily, do they need it on a phone, and who keeps it current?
Three
Online certification and training
We can help start to finish
We have built and run our own certification course on Thinkific, so this is a road we have already travelled rather than one we would be learning on your project. At this stage the useful question is not what the course should become, but what you are starting with.
What we would do
- Structure the curriculum into modules, with knowledge checks between sections so the standard behind the certification is preserved rather than diluted.
- Build it on its own address, separate from the store. That adds nothing to the site's load, which matters given the current speed issues, and it means the training does not depend on the platform decision at all.
- Connect completion back to the account. Finishing certification can be what sets a professional's pricing level, turning training into the route to opening an account.
- Help develop the content itself, not only the platform. Once we are working on your messaging, the same team can script modules, write the knowledge checks, and turn existing protocols into teaching material. We can also work alongside your education consultant rather than in place of them.
- Support the production, or fit around whoever is filming and editing. Platform cost is modest, in the region of $49 per month.
What we need to know
- How much of the course already exists in usable form, and how much would need developing from scratch?
- Who owns the curriculum taught at the institute today?
- Is any of it recorded, or does it exist only as live delivery, slides, and written protocols?
- Who would appear on camera, and are they available?
- Does the certification need outside accreditation, or is it your own mark?
- Must any part of it remain hands on?
- Has the parent company agreed that certification can move online?
Why there are no numbers here yet. Each of these three changes shape considerably depending on the answers above. A quote written before them would be a guess dressed up as a price, and you would end up renegotiating it later. One working session with whoever knows the customer process and the training content would let us scope and price all three properly, and we would rather spend that hour than have you spend the difference.