Coming Soon: Phases 4-5 | Rumzer website iterations

01Where the site goes next

After Phases 1 and 2, the three versions look finished and are tuned for search, but they stand still. Articles only appear when someone writes one, and a filled-in contact form goes nowhere. The next two phases fix both.

Phase 4: automated blog

Finds compliance topics worth writing about, gathers the sources, and publishes a new article in Rumzer's voice on a schedule.

Phase 5: poor man's CRM

Captures every inquiry, replies straight away, offers a call, and follows up with a short email series, in a form Zoho CRM can take over later.

CRM (customer relationship management): a system that keeps track of every person who contacts a business and what has happened since: when they wrote, what they were sent, whether they booked a call.

02Phase 4: a pipeline of article topics

The blog starts from what the site already covers. Every regulation Rumzer's products handle is a candidate topic. Phase 2 left a head start: a research file per regulation, a list of official pages to watch for each one, and a backlog of topics that did not get their own page yet.

Pick a topic→Check for recent developments→Save the sources→Queue for writing

Topics come from the site's regulations, such as REACH, PFAS reporting and Prop 65, and from the Phase 2 backlog: EU POPs, CBAM, end-of-life vehicles, ship recycling, conflict minerals, batteries, the Digital Product Passport and CLP.
Recent developments: for each topic, the pipeline checks the official pages on its watch list for news, such as a new deadline, an amendment or a newly listed substance.
A lasting source library: the pages it finds are saved as plain-text copies in a folder per topic. The article is written from that library, and the library stays behind as the record of what each article relied on.

Pipeline: a fixed series of steps where the output of one feeds the next, like an assembly line. Topics go in at one end and ready-to-write source packs come out at the other.

Markdown: a simple text format that uses marks like # for headings. Saving web pages as Markdown keeps their words and structure without the clutter, so they stay readable for years and are easy for software to process.

03Phase 4: publishing on a schedule

One article every 7 days by default. A scheduler takes the next topic from the queue and starts the writing step.
Manual trigger: an article can be written at any time without waiting, for example when a regulation changes.
All three versions at once: the blog already lives in the shared content folder, so each new article appears in the Zoho Desk, Airtable and Gusto versions together, each in its own style.

Scheduler: a timer that runs a job automatically at set intervals, the way a phone alarm repeats every morning.

A natural extra: the same watch lists can flag when a date on one of the eight regulation pages goes out of date, so "last reviewed" stays true.

04Phase 4: writing in Rumzer's voice

The historical materials include compliance articles written for Rumzer, such as "Prop 65: (How) Does It Work?" and the "REACH Revisited" series. Their voice is the model: authoritative, practical, written for manufacturers, and clear about what a rule means for them.

A style guide drawn from those articles sets structure, tone, length and how sources are cited.
Enforcement by a language model: every draft goes through Qwen 3.8 Flash, which checks it against the style guide and revises it until it matches.
Grounded in sources: drafts are written from the saved source library, not from the model's memory, so every claim can be traced to a saved page.

Large language model (LLM): software trained on large amounts of text that can write, summarize and edit. Qwen 3.8 Flash is a fast, low-cost model of this kind. Here it acts as an editor that holds every article to the same voice.

05Phase 5: capturing every inquiry

Today the contact form, the Zoho version's sign-up card and the Gusto version's questionnaire check what people type but send nothing. Phase 5 puts a small database behind the site so every inquiry is kept, whether it comes from a form or an email link.

Database: an organized store of records, like a spreadsheet that software can search and update reliably. Each inquiry becomes a row: who, when, from which page, what they asked.

The site will also be hosted so anyone with the link can use it, in the simplest free setup available. It stays separate from rumzer.com.

06Phase 5: automatic reply and follow-up

Inquiry→Thank-you email→Book a call→Emails 1–5, every N

Instant acknowledgement: the person gets a thank-you email as soon as they submit.
Book a call: that email includes a way to pick a time. For now bookings are simply recorded in the database, not linked to a calendar.
A five-email series: after that, one email goes out every interval of N, for five emails in total. Each introduces Rumzer's concepts and products a step further.
Adjustable timing: N is a setting stored in the database and can be minutes, hours or days. Minutes suits testing and days suits real use.

Drip campaign: a series of emails sent automatically at set gaps after someone signs up, so they learn about a company gradually instead of all at once.

07Phase 5: built to hand over to Zoho

The in-house setup is a stepping stone. Everything is designed so Zoho CRM can take over the whole flow later, including receiving inquiries, sending the emails and tracking bookings.

Zoho-shaped data: records use fields that line up with Zoho CRM's leads and contacts, so moving them is an import rather than a rebuild.
Portable emails: the five follow-up emails and the thank-you email are stored as templates that can be recreated as a Zoho campaign.
Two migration guides: one for moving the existing data into Zoho, and one for switching the live pipeline over so Zoho handles new inquiries directly.

Rumzer's current site already sends its forms to Zoho Forms, so ending up in Zoho keeps the company on tools it already uses.