Address
Electronic City, Phase 1
Bengaluru - 566 100
Work Hours
Monday to Friday: 9 AM - 6 PM
Schedule a Demo
Most Indian SMBs and boutique agencies do not fail at “being organised.” They fail at three separate piles: WhatsApp promises with no owner, Drive folders named after whoever last uploaded a ZIP, and website edits that go live with no note of what changed. Motivation posters and “make your bed” advice do not fix that. A small, named stack does.
This rewrite replaces a self-help fluff post (“organizing things better”) with a practical 2026 ops setup for client delivery and website work: Drive naming that survives handoffs, a task tool with dates, Keep for capture, a client update cadence, a website change log, and a weekly 30-minute cleanup. Pair capture with our Google Keep workflow for client work and dated delivery with our Todoist setup for small teams.
Who this stack is for
- Indian SMBs and agencies with roughly 2–15 people juggling retainers, one-off projects, and a live WordPress (or similar) site
- Founders or ops leads who currently track work in WhatsApp + a messy Shared Drive and wonder why nothing is “done”
- Teams that need client updates and website changes documented without buying a full agency OS
Skip this if you already run a locked PM tool, a formal DAM, and a staging → production pipeline with tickets for every change. You already have the discipline — this article is the lightweight version for everyone else.
The three piles: tasks, files, updates
Organising “things” is vague. Split the work into three piles and give each pile one home:
- Tasks — dated work with an owner (Todoist or equivalent). Not a chat thread.
- Files — briefs, assets, invoices, and site exports in Google Drive (or OneDrive) with a naming rule clients and freelancers can follow.
- Updates — what you told the client this week, and what changed on the website (change log + staging notes).
If a promise lives only in WhatsApp, it is not organised — it is hope. Move outcomes into the stack the same day.
Step 1: Drive folders and naming that survive handoffs
Pick one Shared Drive (or a single team Drive root). Do not invent a new top-level folder per mood. Use a tree people recognise on an invoice:
- 00_Clients — one folder per active client (short invoice name: Acme_Co, not “New folder (3)”).
- Inside each client: 01_Brief, 02_Assets, 03_Delivery, 04_Admin (contracts, GST invoices, access notes — no passwords in plain Docs).
- 10_Internal — SOPs, templates, brand kit exports, proposal shells.
- 20_Website — staging notes, change log Doc, export/backups pointers, plugin/theme licence PDFs.
- 90_Archive — finished clients and dead projects moved quarterly so search stays honest.
File naming (copy this): YYYY-MM-DD_Client_Deliverable_vN.ext — e.g. 2026-09-16_Acme_Homepage-copy_v2.docx. Date first sorts chronologically; version last stops “final_FINAL2”.
Rewire tip: Pin a one-page “Where things live” Doc at the Drive root. New freelancers should not need a Slack archaeology session to find the logo pack.
Step 2: Tasks in Todoist (Keep for capture)
Do not rebuild your brain inside Drive comments. Split capture and delivery:
- Google Keep — sticky capture from calls, voice dumps, waiting-on-client notes — see the Keep workflow
- Todoist — projects per client + ops buckets, one owner, real due date — see Todoist for small teams
- Drive — the file the task points to, not a second task list
Morning rule: empty Keep “due this week” items into Todoist with a project and date. Title = verb + object (Send homepage copy v2 to Acme). Link the Drive file in the task description. Never paste OTPs or passwords into tasks — point to a password manager.
If you already use Asana or ClickUp for multi-stage pipelines, keep that as the delivery board and still use Keep for phone-first capture. The rule is the same: one system of record for dated work.
Step 3: Client update cadence (so WhatsApp stops being the CRM)
Clients do not need daily essays. They need a predictable pulse. Pick a cadence and put it on the calendar:
| Engagement type | Cadence | What you send | Where it lives |
|---|---|---|---|
| Active build / redesign | 2× per week or after each milestone | Done this period, blocked on them, next decision | Email or shared Doc + Todoist comment link |
| Retainer / care plan | Weekly or fortnightly | Hours used, changes shipped, open risks | Short email + line in website change log |
| Quiet month | Monthly check-in | Uptime/backups OK, one improvement offer | Email; archive in client 04_Admin |
Template three lines only: Shipped / Waiting on you / Next. Attach or link the relevant Drive folder — do not re-upload the same ZIP into WhatsApp every Friday.
Rewire tip: Create a recurring Todoist task per client: “Send Acme weekly update.” If the update is skipped, the tool shows it — chat will not.
Step 4: Website change log and staging notes
Website work goes sideways when “someone changed a plugin” has no owner and no rollback note. Keep a single Google Doc (or Notion page) per site:
- Change log table: Date | Who | Environment (staging/live) | What changed | Ticket/task link | Rollback note
- Staging notes: URL, who has access, last sync from live, known differences (forms, payment gateways, cache)
- Before any live change: backup or host snapshot pointer, staging verified, client approval if visual/copy
- After go-live: one line in the change log within 15 minutes — not “we’ll document it later”
Store the Doc in 20_Website (or inside the client folder if you manage many sites). Point Todoist website tasks at the Doc row, not at a vague “fix site” title.
If you have no staging yet, still keep the change log for live edits. Discipline beats a fancy environment you never write down.
Weekly 30-minute cleanup checklist
Without a review, Drive and Todoist become junk drawers again. Block 30 minutes every Friday (or Monday morning) for the people who own delivery:
- WhatsApp → stack — any promise from the week still only in chat gets a Todoist task or a deliberate “won’t do.”
- Keep → Todoist — empty orange / due-this-week Keep notes into dated tasks.
- Todoist Inbox + overdue — project, date, or delete; reschedule honestly.
- Drive hygiene — move finished delivery ZIPs into 03_Delivery or Archive; kill duplicate “final” files; confirm active client folders still match the invoice list.
- Client updates — send any missed weekly/fortnightly notes; log them under 04_Admin.
- Website change log — every live tweak from the week has a row; staging notes still accurate.
- Capacity glance — if one person owns half of next week’s hard deadlines, redistribute before the week starts.
Thirty minutes is enough for a team under ~15. Longer cleanups usually mean the folder tree is too deep or tasks are still paragraphs.
What not to do (the fluff traps)
- Do not organise art supplies, sock drawers, or morning routines and call it business ops — that was the old post’s problem.
- Do not add a fourth tool “for organisation” every quarter. Finish Drive + Keep + Todoist (or your one PM) for 90 days first.
- Do not keep parallel truth in WhatsApp, email, and a sheet. Chat is transport; the stack is record.
- Do not store client passwords in Drive Docs or task comments.
2026 SMB checklist
- Drive tree: Clients / Internal / Website / Archive with dated file names
- Keep for capture; Todoist (or one PM) for dated delivery — see the linked guides
- Written client update cadence per engagement type
- Website change log + staging notes Doc, updated the same day as go-live
- Recurring 30-minute weekly cleanup on the calendar
FAQ
Do we need Notion if we have Drive + Todoist?
Only if you need a wiki or long specs people search weekly. Drive holds files; Todoist holds dates. Notion is optional — not a third mandatory pile.
What if the client insists on WhatsApp?
Use WhatsApp for speed, then mirror decisions into Todoist and the update email the same day. Tell them the weekly note is the official status so chat scrollbacks are not the contract.
Can one person run this stack?
Yes — solo consultants benefit most from naming rules and a change log. The weekly cleanup still matters; skip the capacity redistribute step.
How is this different from “just being tidy”?
Tidiness is vibes. This stack names where tasks, files, and client/website updates live, who owns them, and when you review. That is ops, not self-help.
Conclusion
Keeping client and website work organised is not about motivational habits. It is a simple stack: Drive folders and dated names for files, Keep for capture, Todoist for dated tasks, a predictable client update cadence, a website change log with staging notes, and a weekly 30-minute cleanup so the system stays trustworthy. Copy the tree and the checklist this week — then stop reinventing “organisation” every time a project feels chaotic.
If you want WordPress, client intake, and delivery handoffs set up so fewer promises die in chat, contact Rewire India.