The most common question we get from other founders is some version of: “How are you building 150 modules with the team you have?”
The honest answer is that the question is wrong. We're not building 150 great modules. We're building 150 good-enough modules on top of a small number of really well-built foundations. That distinction is the entire architecture.
The picking process.
We started with one rule: a module belongs in Mewayz only if it removes a SaaS subscription our target customer is already paying for.
Not “might pay for.” Not “could imagine paying for.” Currently paying, today, with a credit card on a recurring basis. That filter eliminates 80% of the modules we could theoretically build.
The remaining 20% — about 150 categories — are the ones where our typical SMB customer is currently paying $25–500/month somewhere. CRM, HR, accounting, support, projects, marketing — the obvious ones. But also POS, bookings, contracts, forms, surveys, knowledge bases, NGO management, call hubs, AI document generators, training centers.
Every module in Mewayz has to point at an invoice in the customer's existing software bill.
What we don't build.
Worth noting what's not in Mewayz, deliberately:
- Specialty creative tools. Figma, Adobe, Logic — single-purpose creative tools where excellence dominates. Bundling-in would be insulting to the categories.
- Developer infrastructure. GitHub, Sentry, Linear. Adjacent universe, different buyers, different workflows.
- Communication platforms. Slack, Zoom. Could be table stakes one day, but the network effects are too strong to dent now.
- Enterprise IT. Identity, SSO, MDM. We integrate with Okta etc; we don't replace them.
The architecture: three layers.
The trick to shipping 150 modules without 150 teams is that most modules aren't independent products. They're configurations over shared primitives.
We built three foundation layers that every module uses:
Layer 1: The data spine
A unified data model across the platform — Contact, Company, Item, Document, Event, Money. Every module reads and writes through this spine. The CRM's “contact” is the same record as accounting's “customer” and helpdesk's “ticketer.” No syncing, no duplicates.
Layer 2: The workflow engine
One workflow runtime that handles all the cross-module actions. Quote → invoice → payment → commission → payroll. Lead created → email sent → task assigned. Ticket opened → SLA timer → escalation. All the same engine, configured per module.
Layer 3: The UI kit
Every module is built from the same 40-or-so components — list view, detail view, kanban, calendar, form builder, report builder. New modules ship by configuring these components, not by designing screens from scratch.
The roadmap.
We shipped roughly 90 modules in v1 and the next 60 in v2. The pace is roughly 4–6 new modules per month, plus continuous depth-work on the most-used existing modules.
The modules ship in an order set by three signals:
- What customers are asking for, weighted by deal size. A request from a 200-person agency moves faster than ten requests from solo users.
- What replaces the most expensive existing subscription. A new module that lets customers drop a $300/month tool wins over one that drops a $30/month tool.
- What unlocks a vertical pack. Shipping “PMS” lets us launch a Hotel pack. Shipping “Matter Management” lets us launch a Law pack. Vertical packs convert at 3× the rate of horizontal modules.
Module quality, honestly.
Different modules are at different levels of polish. The core 30 — CRM, HR, accounting, helpdesk, projects, marketing — are genuinely competitive with the best-in-class standalone tools at the SMB tier.
The next 50 are at “good-enough-for-most-customers” quality. They cover 80% of the use cases of standalone products. The remaining 70 are at “table-stakes” — they do what they need to do, they don't surprise on the upside.
We're upfront about this. The pitch isn't “every module is the best.” The pitch is “all the modules connected, at one price, with no SaaS sprawl.” If you need the best-in-class spreadsheet, use Excel. If you need the best-in-class deck tool, use Pitch. If your trade-off is “good across all of them, one bill,” you're our customer.
What we learned the hard way.
Three things, looking back:
- Module count is a vanity number. 150 sounds impressive in marketing. What customers actually care about is whether the 12 modules they use are good. Internally we obsess over module depth for the top 20, not count.
- The data spine took longer than the modules. 18 months on foundations, 6 months on the actual surface area. If we rebuilt from scratch we'd spend even more on the foundations.
- Migration tooling matters as much as the modules. The hardest part of getting a customer onto Mewayz isn't building the destination — it's moving their data from the seven incumbents. We spent the last six months building 40+ migration tools. Each one un-locks roughly 4% more conversion.
None of this is glamorous. None of it makes for good launch tweets. But it's why v2 ships at the scope it does. The next 18 months are about depth on the modules customers actually use, not new module count.