The running record of the project to automate the busywork out of Smita's RoofIgnite workday. It grows as the conversation does — start with the update log below to see what's new since you last read.
Every time this doc changes, a dated entry lands here saying what was added, and the affected sections get a matching date tag. Read the newest entry, jump to its sections, done.
NewThe docs moved to their own site — this one — so the worksheet finally works the way it was meant to: tap an answer, hit Save, and it's stored instantly with a timestamp. Change or remove answers any time; nothing is ever silently deleted. Same look, same links between docs, no accounts needed.
The docs became directly shareable pages and the worksheet became an interactive page — tap-to-answer questions with timestamped, changeable, removable-with-review responses. The Drive folder stays as the backup copy.
All docs rebuilt in RoofIgnite branding — palette and typography sampled from the live roofignite.com site — after a formatting overhaul (proper section bars, styled tables, callout panels, answer boxes). Content unchanged; only the look is new.
Docs now live in a shared Google Drive folder ("SmitaVA") so Smita can be given access by email — no public link — and can type answers directly. Added the SmitaVA Worksheet there: her fill-in doc for the time audit, the five gating questions, and a tool inventory. The Drive copies are the canonical ones for Smita; this page mirrors them.
First entry. Captured the two voice memos that started this, the diagnosis, the three-layer recommendation, the options weighed, guardrails, and the open questions awaiting answers.
Two voice memos from Smita to her brother, and his replies, kicked this off.
"What I want to avoid is clicking and typing. If it could take those two things off my plate, I feel like I could work more efficiently… I'm not letting it do things on its own — I'm telling it what to do."
The ask: an AI she can direct by voice while working — open Gmail, draft this email, send it to so-and-so — with her staying in control of every action. The reply: have it draft multiple things (invites, messages) that she reviews before anything goes out, and run a time audit of a typical workday to find where the hours actually go.
"Pull crap from Gmail, GHL… Slack, ClickUp — just kind of having everything in one place… What about organizing the information per account? I just need a customized system."
ChatGPT pointed her at Gumloop for stitching tools together, and Notion came up for per-account organization. The reply: worth a look, but also ask for free and secure options.
The clicking and typing is the symptom. The real problem is that Smita is the integration layer: Gmail, GoHighLevel, Slack, and ClickUp don't talk to each other, so she pulls context from four systems by hand, re-assembles it in her head per client, and hand-produces every output — emails, invites, tasks, updates. In memo 2 she diagnosed it herself: everything in one place, organized per account, a customized system.
That rules out one tempting architecture: a bot that literally drives her screen. It would be slow, brittle, break with every UI change — and it automates the symptom. The right solution talks to her tools through their APIs, and keeps her exactly where she wants to be: in the approval seat.
A conversational assistant — typed or dictated, macOS dictation covers voice for free — built in three layers, in order of value:
"Draft a reply to the Hendersons about their renewal." It produces the email, the tentative calendar invite, the ClickUp task — and Smita reviews and green-lights each one. Nothing goes out without her. Her human-in-the-loop instinct from memo 1 is a hard design rule here, not a nice-to-have.
A living dossier per account, kept fresh from GoHighLevel, email threads, and ClickUp activity. Drafts arrive with context already in them, and "everything on client X before this call" takes one sentence instead of twenty minutes of tab-hopping. This is the "customized system" from memo 2, made real.
Each morning: what changed per client, which accounts went quiet or show risk signals, where there's an upsell or cross-sell opening. This is the layer that buys back time for the strategy work — and the piece nobody had suggested yet.
| Option | What it gets you | Verdict |
|---|---|---|
| Claude + connectors | Gmail, Calendar, and Slack connect today; ClickUp has an official MCP server; GoHighLevel has a real API with community servers. With dictation, ~70% of layers A and B — this week, near-zero code, no maintenance burden. | Do first — Phase 1, regardless of what comes later. |
| Custom build (SmitaVA) | A purpose-built agent on the same APIs, with an approval gate on every outbound action and a scheduled morning brief. The only path to layer C and RoofIgnite-specific workflows. | Phase 2 — shaped by what Phase 1 teaches. |
| Gumloop / Zapier / Make / n8n | Pipeline tools: fixed triggers like "new lead form → do X→Y→Z." Not the interactive tell-it-and-review experience Smita described; Gumloop also routes client data through another third party. | Complement at most — if ever needed, self-hosted n8n is the free/secure pick. |
➡ Smita answers these in the SmitaVA Worksheet — tap answers right on the page; they save with timestamps. (A copy also lives in the shared Google Drive folder as backup.)
Any policy on third-party AI touching client data? Can Smita get GoHighLevel API access for her sub-account? This gates everything else.
The one-day time audit from memo 1's reply: email drafting vs. scheduling vs. cross-system lookup vs. reporting. The top two by hours pick the first build.
Is the SmitaVA custom build the plan, and is her brother signing up to be her IT department for it?
Is roughly $20–30/month for a subscription acceptable, or does "free" need to be literal?
Dictation-into-chat is easy and free. A true hands-free voice agent on iPhone is a much bigger lift for marginal gain at a desk job.
No decisions recorded yet. As choices get made — tools adopted, phases started, questions answered — they land here with a date, so this section becomes the project's memory.