Multi-tenant SaaS platform
MZC Core
A custom multi-tenant SaaS platform for real estate and service-based businesses that need CRM workflows, branded microsites, client portals, document handling, subscriptions and AI-assisted productivity in one connected system.
Overview
More than a website.A connected operating system.
MZC Core was built for businesses that need more than a website or a basic CRM: a place where agencies and professional-services teams manage enquiries, clients, documents, workflows, team members, branded microsites, subscriptions and customer communication together rather than in six tools that do not talk.
It is designed as a multi-tenant system: each organisation works inside its own isolated workspace while sharing a single codebase, so a new customer is an onboarding flow rather than a deployment.
MK TechLAB's role
Architecture through to launch readiness.
MK TechLAB led the technical architecture and product engineering: the tenant model, workflow logic, role-based access, subscription foundations, AI-assisted features, transactional email flows, compliance-readiness documentation and the launch-readiness auditing that governs what ships next.
Built by MK TechLAB and owned by MOZAIC SL, where Mike Koszo is technical co-founder. PASKU.CO, a boutique property consultancy on the Costa del Sol, is the first organisation on the platform.
The problem
Most firms run on four toolsand none of them agree.
The cost is not the software. It is the lead nobody followed up, the document somebody could not find, and the fortnight of admin a year that goes into keeping four systems roughly in step with each other.
- Spreadsheets, shared inboxes and a website form that emails somebody.
- Documents in one place, client history in another, follow-ups in a third.
- Every vertical working differently, so a generic CRM fits none of them.
- No single view of where an enquiry came from or what happened to it.
What MK TechLAB built
One platform.Eight things it has to do at once.
Multi-tenant workspaces
Each organisation operates inside its own workspace on a shared codebase, with data separated at the organisation level rather than filtered in the interface.
Role-based access
Owners control what each role can do. Agents see their own records. Platform-owner tooling is separate again, and admin actions are logged with timestamps and attribution.
Lead and client workflows
Capture, assignment and attribution, with a buyer timeline that follows a person from first enquiry through to the documents they signed.
Branded microsites
Every professional gets a public, SEO-first microsite generated from their own profile and listings, on its own subdomain provisioned automatically.
Client portals
Clients reach their own portal through a tokenised link rather than an account and a password, with document access on signed, time-limited URLs.
Subscription foundation
Trial activation, onboarding, and a Stripe-backed subscription lifecycle, with per-organisation feature flags enforced in the sidebar, the page and the API alike.
AI-assisted, human-review-first
Content and support tooling that drafts but never publishes. Nothing generated goes live without a person approving it, which is a product decision rather than a limitation.
Multilingual structure
Six languages live, built into the product structure rather than bolted on, with per-locale routing across the marketing site and the platform.
Built for every vertical
One platform.Every profession.
Each vertical gets purpose-built tooling inside the same system, rather than a separate product or a fork of the codebase.
Real estate
Law offices
Developer sales
Relocation
Designers
Marketing agencies
Mortgage
Mortgage brokers
Asset management
Technical approach
Decisions that are hard to reverseget made early.
Tenancy in the data layer
Isolation is enforced where the data lives, not where it is displayed. An interface filter is a presentation choice; an organisation boundary is a guarantee, and only one of those survives a new endpoint written in a hurry.
Feature flags at three levels
A capability a plan does not include is absent from the navigation, returns a 404 at the page, and is refused at the API. Hiding a menu item is not access control.
Subdomains provisioned, not configured
A new organisation gets its microsite subdomain created programmatically rather than by somebody editing DNS, which is what makes onboarding a self-service flow instead of a support ticket.
Invitations that expire
Invite tokens have a fourteen-day life and return 410 Gone afterwards, so a link forwarded a year later fails closed rather than granting access to whoever now holds it.
Encrypted third-party keys
Where an organisation brings its own AI provider key, it is encrypted at rest, masked in the interface, and decrypted only server-side at the moment of use.
Consent captured on every lead path
Not on the main form only. Every route by which a person can enter the system records consent, because the one that was missed is always the one that matters later.
What this demonstrates
Not a website with a login.A platform with a business on it.
MZC Core is the deepest thing MK TechLAB has built: a tenant model, a permission model, a billing lifecycle, a public-facing microsite generator and an AI layer that defers to a human, all in one codebase with a real organisation working inside it.
It is the answer to the question a small business asks before commissioning software: whether the person building it has done this at a scale where the decisions are hard to reverse. Most of what is on this page is not visible in the interface, tenancy enforced in the data layer, flags checked at three levels, invitations that expire, keys encrypted at rest. That is the part that decides whether a platform is still standing in three years.