Confidential — Pre-Meeting Brief

Chatworks Investor Questions

Three strategic questions for Brett Goldberg, Founder of Chatworks, ahead of a meeting to explore investment and partnership opportunities.

Brett Goldberg Founder, Chatworks (Blue Banana Software)
Johannesburg, SA Meta Tech Partner
July 2026 Maverix Studio

Context

Brett Goldberg is a systems integration and ERP specialist with 15+ years of experience, primarily in SYSPRO integrations through his company Blue Banana Software. In 2025, he launched Chatworks as a WhatsApp Business API-powered communication platform built specifically for the South African market.

Chatworks is an Official Meta Tech Partner offering a consolidated inbox, automation workflows, campaign management, payment link integrations (Peach Payments), and e-commerce connectors (Shopify, WooCommerce). The business is a one-man show with 2-10 employees, operating on once-off setup fees (R9,995-R14,995) and monthly subscriptions (R1,995-R2,495/mo). Brett is seeking investment.

2025
Founded
R2,495
Monthly entry price
Meta
Tech Partner status
1
Platform vs. Workflow Canvas — Why build infrastructure when you could build on top of it?

You've built Chatworks as a platform — consolidated inbox, automation engine, campaign manager, payment integrations. That's a significant technology investment for a one-man operation. Meanwhile, the SA market already has established BSPs (Clickatell, BizAI, 360dialog) and Meta's own Cloud API providing the infrastructure layer.

An alternative approach would be to build a workflow and integration canvas on top of existing BSP infrastructure — similar to how Zapier sits on top of APIs without owning the API layer. This would mean less infrastructure to maintain, faster time-to-market for new features, and the ability to be BSP-agnostic (let the client pick the cheapest/best BSP, while Chatworks owns the workflow and business logic layer).

Specifically

What is the strategic rationale for owning the infrastructure layer (inbox, routing, API management) versus owning only the workflow/integration layer on top of existing BSP APIs? What does building the platform cost you in terms of speed, focus, and capital that a canvas-first approach would not? And if a major BSP like Clickatell or Twilio launched a native workflow builder tomorrow, where does that leave Chatworks?

Why we're asking

The WhatsApp BSP market has 400+ providers globally with well-funded incumbents (Twilio at $4B+ revenue, Infobip, Clickatell at $63M). Competing at the infrastructure layer against funded players is capital-intensive and risky. The workflow/integration layer — where business logic, CRM connectors, and process design live — is far less crowded and is where implementation value actually accrues. We want to understand whether the platform is a moat or a burden.

2
Ideal Customer — Who stays, who churns, and where does the revenue actually compound?

Chatworks lists eight target industries on its website — retail, healthcare, real estate, financial services, logistics, hospitality, education, and automotive. That's a very broad surface area for a one-man show. Each vertical has fundamentally different WhatsApp use cases, compliance requirements, and integration needs.

For an investor evaluating this business, the critical question is unit economics by customer type: Which customer profile has the highest lifetime value? Which has the lowest acquisition cost? And critically — which customers stay past month three?

Specifically

Of the clients you've onboarded to date, can you walk us through: (a) the top 20% of clients by revenue — what do they have in common? (b) the bottom 20% — why did they sign up and why did they leave (or downgrade)? (c) What is your current monthly churn rate, and what does the retention curve look like at 3, 6, and 12 months? And (d) if you had to narrow to a single ICP for the next 12 months, which vertical and company size would it be — and why?

Why we're asking

SA's WhatsApp market is massive (96% penetration, 29M users), but "everyone uses WhatsApp" is not a go-to-market strategy. A one-man operation cannot serve eight verticals effectively. Understanding where revenue actually compounds — and where it doesn't — tells us whether the business is fundable at scale or remains a lifestyle services company. The answer also reveals whether Chatworks is a product business (recurring revenue, low marginal cost) or a services business (revenue tied to Brett's time).

3
Client Onboarding — From signed contract to live WhatsApp, what does the journey look like and where does it break?

Your pricing page advertises "up and running within 5 days" for the entry package. That's an aggressive promise given everything that has to happen: Meta Business verification (1-5 business days alone), WABA setup, display name approval, template creation, workflow design, integration with the client's CRM/payment gateway, and team training.

The onboarding process is where most WhatsApp implementations stall. Meta verification backlogs, template rejections, unclear ownership of the WhatsApp number, and clients who haven't prepared their customer data are all common friction points. How Chatworks handles this determines whether the business scales or hits a ceiling tied to Brett's personal capacity.

Specifically

Can you walk us through the exact onboarding journey for a new client — from the moment they sign to the moment their first WhatsApp campaign goes live? Where are the recurring bottlenecks? How much of the process is automated versus requires your personal involvement? Have you documented the playbook so that someone else could deliver it, or is the institutional knowledge entirely in your head? And what happens when a client needs ongoing support — who handles that at 9pm on a Tuesday?

Why we're asking

For a one-man show seeking investment, the onboarding process is the single biggest constraint on growth. If every new client requires 10-15 hours of Brett's time in the first week, the business cannot grow beyond what Brett can personally deliver. An investable business needs a repeatable, delegable onboarding process — documented playbooks, self-serve components, and a support model that doesn't bottleneck on the founder. The answer to this question tells us whether investment capital would unlock scale (by hiring people to execute a proven process) or merely fund more of Brett's time (which doesn't compound).