Timeline bands by complexity
Band A — single trigger, one CRM write, one notify: often 1–2 weeks after access. Band B — branching, Sheets staging, WhatsApp template: commonly 3–5 weeks. Band C — multi-system migration or Playwright portals: 6–10+ weeks with parallel-run.
These are working calendars, not billable-hour math. Waiting for a client’s GST portal OTP or board approval to buy Zapier sits on the critical path even when engineers are free.
Brevia package floors (Zapier ₹15k+, n8n/Make/WhatsApp/chatbot ₹18k+, Playwright ₹25k+) buy a scoped outcome, not unlimited change requests. Timeline quotes assume frozen scope after discovery.
What “week one” usually contains
Kickoff, access checklist, sample payloads, field dictionary draft, and a success metric in numbers — response time, completeness, or hours saved — not “make it smart.”
What “go-live week” must include
Monitoring alerts, pause instructions for ops, and a named human who can disable the flow during a bad campaign. Without that, you launched software, not an operable system.
Phase 1: Discovery that actually shortens the build
Good discovery feels slow and saves rework. Map the painful workflow end-to-end, list apps, estimate monthly volume, and identify irreversible actions. Decide whether Zapier, Make, or n8n fits — n8n vs Zapier if you are stuck.
Capture exception paths: duplicate leads, missing phone, after-hours enquiries. Automating only the happy path creates silent failures that sales discovers on Monday.
Output of discovery should be a one-page scope: triggers, steps, out-of-scope list, and acceptance tests. That document is what keeps “can we also sync inventory?” from adding three weeks mid-sprint.
- Credential owners named with backups
- CRM mandatory fields agreed with sales
- WhatsApp template copy drafted early for approval queues
- Success metric and kill-switch owner written down
Red flags that predict slip
Two CRMs “both kind of live,” founders promising API access they do not control, and no one who can approve message templates. Pause commercial kickoff until those clear.
Phase 2: Build and staging
Build against staging credentials whenever the app allows. Use sample leads that include ugly real-world data — emoji in names, missing email, duplicate phone formats (+91 vs 0).
For n8n Automation, decide hosting early so SSL and backups are not week-four surprises. For Zapier and Make, enforce naming conventions from day one so task history is readable.
LLM or agent steps need a mini evaluation set in this phase — do not leave scoring for production week. See the agent vs workflow framing in AI agents vs workflow automation.
Typical build blockers we see
Sandbox CRM missing custom fields that production has, webhook URLs blocked by IT, and Sheets tabs that marketing renames without notice. Freeze tab names like API contracts.
Documentation that belongs in the build ticket
Field map screenshot or table, retry behaviour, and who gets failure Slack alerts. Handover starts during build, not as an afterthought PDF.
Phase 3: Parallel-run and cutover
Run old manual or old zap path beside the new flow. Diff CRM records daily. Only cut traffic when mismatches are understood — not when the demo looked pretty.
Migrations deserve extra caution: How to migrate from Zapier to n8n without breaking CRM outlines inventory and decommission steps. Big-bang Friday cutovers are a known failure mode.
WhatsApp cutovers need message log review so customers do not get double templates. Keep a suppression list for anyone already contacted manually that day.
Minimum parallel-run checklist
Same lead ID appears once in CRM, notify channels match, error rate trending down, and sales signed a one-line acceptance in writing or Slack.
What slows Indian SME automation projects
Access latency beats engineering latency. Meta verification, bank portal 2FA held by one director, and agencies who share logins over WhatsApp all steal days.
Process ambiguity is next: sales and marketing disagree on lead stages; automation encodes the louder opinion and breaks trust. Facilitation is part of timeline, not “soft skills fluff.”
Festival calendars matter. Do not schedule cutover the week before Diwali peak ads unless rollback is rehearsed. Tamil Nadu and national campaign spikes are predictable — plan around them.
- Single-threaded approvers on holiday
- Changing scope after first UAT
- No staging environment for CRM
- Unofficial WhatsApp tools discovered mid-project and rejected
How to compress the calendar ethically
Pre-approve templates, grant least-privilege API users before kickoff, and freeze field names for the sprint. Paying for more developers does not unlock Meta’s review queue.
How “rush fees” actually get used
Extra coverage for evening testing and tighter project management — not magic that skips compliance. If a vendor promises full WhatsApp API live tomorrow with no caveats, be sceptical.
Tool-specific calendar notes
Zapier: fastest for clean SaaS; watch task design reviews when Paths multiply. Make: scenario complexity can hide debug time — budget UAT. n8n: hosting and credential stores add front-loaded days if self-hosted.
Chatbots and WhatsApp: conversation design and template approvals dominate. Website FAQ bots can ship faster than compliant outbound follow-up — see Website chatbot vs WhatsApp.
Playwright: brittle selectors and portal UI changes mean longer hardening and monitoring setup. Floors from ₹25,000 OTP reflect that reality on Playwright Automation.
When self-hosting extends the plan
Add VPS provisioning, backups, and update ownership before counting workflow build days. Details in Self-host n8n in India: VPS cost and risks.
Roles and response SLAs that keep weeks honest
Name a client-side project owner who answers within one business day on access questions. Without that, agency idle time becomes “the automation is slow.”
Brevia replies within one business day from Chennai on Contact. Your internal SLA should match — directors who only check email weekly stretch every phase.
Include sales in UAT early. Ops-only testing misses the “this lead should have been VIP” rules that live in someone’s head.
RACI lite for SMEs
Responsible: automation builder. Accountable: client ops lead. Consulted: sales head. Informed: finance for subscription and OTP invoices. Write it once; reuse every sprint.
What belongs in the weekly status
Blocked access items, test pass rate, open scope changes, and go-live risk — not vanity “percent complete” without a definition of done.
Sample calendars you can show your CEO
Example 1 — Meta lead to Zoho to Slack (Zapier): discovery 2 days, build 4 days, UAT 3 days, parallel-run 5 days. Example 2 — same plus WhatsApp template: add 1–3 weeks for provider and template approval overlap.
Example 3 — Zapier to n8n migration of five revenue zaps: inventory week, rebuild two weeks, parallel-run two weeks, decommission week. Example 4 — Playwright GST download job: discovery plus selector spike, then monitoring week.
These are planning shapes, not contracts. Your volume and compliance constraints move the bars. Cost pairing: AI automation cost in India.
What “fast track” still cannot skip
Credential hygiene, a pause switch, and at least one realistic failure test (bad phone, duplicate lead). Skipping those buys fake speed.
After go-live: the quiet two weeks
Watch failure alerts daily. Expect one CRM field rename or Meta form tweak soon after launch. Budget a hypercare window in the statement of work.
Train the day-two editor with a Loom and a checklist. If only the agency can touch the canvas, your timeline to the next change is forever a ticket queue — hiring advice in How to hire an AI automation company.
- Review first 100 executions for surprises
- Confirm finance sees subscription line items
- Archive obsolete manual SOPs so staff do not double-work
- Schedule a 30-day optimisation pass if volume spikes
When to schedule the next workflow
After the first path is boringly reliable. Stacking three half-done automations is how SMEs conclude “automation does not work.” Hub: AI Automation in India.
When timelines should be revisited
Scope change, new compliance rule, or tool migration mid-flight. Re-estimate in writing; do not absorb infinite change inside the original OTP.
Getting a date you can trust from Brevia
Bring one workflow, volume guesses, and access contacts to a consultation. We return a phased plan with assumptions listed — including what you must deliver to keep the calendar.
Remote delivery across India uses the same playbooks as Chennai onsite kickoffs. Specialty builds link from n8n, Make, Zapier, and WhatsApp pages.
Artifacts we ask for before promising a week number
Sample webhook or form export, CRM field list, and current manual SOP if it exists. Screenshots of the painful process beat abstract wish lists.
Ready to automate one painful workflow?
Tell us your stack — n8n, Make, Zapier, WhatsApp, or Playwright. Chennai HQ · India delivery · reply within one business day.