How It Works
Simple for builders. Scalable for Ritz‑Craft.
From request to deployment in five straightforward steps — no agencies, no long timelines, no confusion.
Every Builder Gets Their Own TMS Instance
When a builder joins TMS, they receive a fully configured website, CRM, and marketing platform — built on the Ritz‑Craft shared core, but customized for them: their logo, their markets, their product offerings, their lead workflows. It’s not a template they manage themselves. It’s a live, operational stack managed on their behalf.
They Ask for What They Need — In Plain Language
There’s no ticketing system, no agency brief, no phone tag. Builders access TMS through a co‑branded chat interface (Ritz‑Craft + MoJo Active). They describe what they want in plain terms.
“I want to run a spring promotion targeting buyers in [county]. I need an email, a landing page, and a Facebook ad.”
“Can we add a follow‑up sequence for leads who haven’t responded in two weeks?”
“Our plan gallery needs to be updated with three new models.”
That's it. The request is in.
AI Helps Refine. Our Team Confirms.
AI helps structure and draft an initial response to the request — catching missing context, surfacing relevant existing assets, and accelerating the scoping process. A MoJo Active team member reviews it, confirms scope and timing with the builder, and gets to work.
This isn’t AI replacing judgment. It’s AI accelerating the team — so builders get faster responses and our team spends time building, not back-and-forth.
Delivered in 2 Business Days (for Standard Requests)
For the large majority of requests — campaigns, CRM automations, new landing pages, content updates, SEO improvements — delivery happens within two business days of scope confirmation. Changes go live in the builder’s actual website and CRM, not a staging environment they never see.
It Goes Live. Documented. Done.
Every change is deployed directly into the builder’s live stack and documented — either inline in the platform or accessible through the TMS knowledge base. Builders always know what was done, why, and how to use it.
Standard vs. Custom — What's the Difference?
Standard requests are well-defined, fit within existing platform capabilities, and don't require custom development.
Think: email campaigns, landing pages using existing templates, CRM workflow additions, form changes, plan page updates.
Custom or special projects involve more complexity — a ground-up microsite, a deep integration with a third-party tool, a major structural redesign.
These are scoped separately with a fixed project fee and a timeline that reflects the work involved.
Both types have a clear answer within one business day of submission.