Growth Engineering & GTM: Local Search Acquisition & Organic Reach
An independent chemistry tutor in Chennai had strong outcomes and no online presence. I built a no-paid-acquisition channel for her: a verified Business Profile, a conversion-focused website and on-page SEO. Local search came first. Calls and enquiries from outside India followed, along with new enrolments from cities beyond Chennai. As her online classes grew, a spin-off product, MeetRoll , came out of it.
Great teaching, invisible online. Parents searched and never found her.
Turn offline reputation into indexed proof: reviews, Maps, one-step enquiry.
200+ enrolments (tutor-reported), 200+ reviews, and a spin-off product.
Problem: a good teacher nobody could find
[PLACEHOLDER: avatar]
"I teach well and my students do well, but parents can't find me online and my visibility is significantly lower than my competitors. I would like to establish a channel through which I can strengthen and enhance my presence."
Independent chemistry tutor · Chennai · Women-owned 💜
| Failure | Why it happens | Effect |
|---|---|---|
| No local visibility | She did not appear in Google Maps or local search, so new students came only through referrals. | Growth capped by word of mouth |
| No trust signal | There were no public reviews a new parent could check before calling. | Hesitation before enquiring |
| No way to enquire | There was no form or clear contact path, so every enquiry needed a phone call. | Lost enquiries |
The core gap was discoverability: the right parent needed a clear path to find her, trust her, and enquire in one step.
Discovery: a visibility and trust problem, not a teaching-quality problem
I started from the tutor's concern, not a solution. I mapped the parent journey (search, compare, look for proof of quality, enquire) and where she was absent from it. Nobody could find her, so nobody could convert.
Research snapshot
Signals behind the first acquisition hypothesis.
Community referrals
The tutor, students and a local parent thread all pointed to referrals as her main acquisition source.
Search and Maps
Her online presence was unindexed; competing Chennai tutor listings were often weak or outdated.
Reputation had no reach
Strong word-of-mouth existed, but parents could not discover it through search.
Make trust searchable
Turn existing goodwill into searchable proof before investing in paid acquisition.
| Audience segment | Where they arrive | Signal tracked |
|---|---|---|
| Local, in-person intent | Google Maps and local search | Direction requests and calls |
| Remote or hybrid intent | Organic search and the website. She already taught a small group (fewer than 10-15 students) online on Google Meet, so this segment existed at a small scale. | Form enquiries and out-of-city enquiries |
Hypothesis & success metrics
If a parent searching for a chemistry tutor can find her, verify her credibility through genuine reviews, and enquire in one step via a verified Business Profile and simple website, then inbound enquiries and enrolments should increase.
- Audience
- Parents new to her
- Intervention
- Search, proof, one-step enquiry
- Success signal
- More enquiries, then enrolments
Constraint: it had to work without ongoing technical or marketing effort from her. So I proved one local channel first, then looked beyond Chennai.
| Metric type | Metric | Why it matters |
|---|---|---|
| Outcome | Student enrolments | The result the tutor actually cares about. |
| Leading | Profile interactions (calls, directions), form enquiries | Show intent before enrolment happens. |
| Discovery | Profile views, search impressions, average position | Show whether the channel is being found at all. |
| Trust | Number of authentic reviews | Show whether a new parent has proof to check. |
Scope, prioritisation & trade-offs
I prioritised with MoSCoW around two constraints: easy for parents to use, and simple enough for a non-technical tutor to run.
| Priority | Requirement | Rationale |
|---|---|---|
| Must Have | Verified Google Business Profile | A discoverable local presence and a trusted starting point. |
| Must Have | Website hosted | One place for information, credibility and enquiries. |
| Must Have | Call, WhatsApp and enquiry form | Parents have different contact preferences; all three were required at launch while keeping follow-up manageable for her. |
| Must Have | Authentic student reviews | "No trust signal" was one of the three core failures, and the hypothesis depends on parents being able to verify her. |
| Should Have | On-page SEO and localised content | Better discovery for local and subject searches; not essential to the enquiry flow. |
| Could Have | Improvements from monthly feedback | Not required to launch; monthly check-in calls created a loop for finding and addressing operational gaps. MeetRoll (spin-off product) originated here. |
| Won't Have | Payment collection through the website | Excluded at the tutor's request and kept outside the initial scope. |
Strategic decisions and trade-offs
MoSCoW set the launch scope; these decisions explain the strategy behind it and the trade-offs I accepted.
| Decision | Why it holds | What I gave up |
|---|---|---|
| Local first, Business Profile as channel one | The biggest gap, measurable, and the fastest low-cost way to validate demand. | Slower expansion; early dependence on Google |
| Organic before paid | Search and Maps gave a measurable path with no paid acquisition. | A slower ramp; rankings are not guaranteed |
| Real reviews only | Credibility mattered more than volume. | Slower review growth |
| A simple site over a platform | The owner is non-technical; complexity would have become her problem. | Fewer features at launch |
| Build instead of adopting an existing add-on | I searched the Marketplace for one that met her requirements and found none that did. | Build and maintenance effort; review dependence on Google |
| An add-on inside Google Meet | Classes already happen in Meet, so an add-on there replaces the screenshot workaround. | Dependence on Google Meet |
Low-fidelity prototypes
Figma
Hero page
Opening screen that introduces the tutor and the primary enquiry path.
Figma wireframes used for structural approval with the tutor before development. Primary layouts only; the final site has more pages.
Solution & go-to-market
A connected system from discovery to enquiry, class delivery and follow-up. Each step feeds the next.
GTM sequence: launch moves
01Google Business Profile
02Website
03Organic search
Results: did the hypothesis hold?
Verdict: Discovery and intent signals held. Enrolment growth is reported by the tutor and cannot yet be attributed to the channel alone.
Insight: Of 2,066 searches that surfaced the profile, about 70% (1,446) were the generic query "chemistry" and only about 20% (412) were the tutor's name. The channel is reaching people who were searching for a subject, not just people who already knew her. 80% of discovery was on mobile search.
No analytics baseline existed before launch (she had no online presence), and enquiries were not tagged by source. The enrolment baseline (about 145) and the ~40% increase are the tutor's reported figures, so these are post-launch indicators, not a causal uplift. Metrics cover different periods based on available Google reports. Calls and directions are part of total profile interactions. Enquiries and enrolments from outside India are tutor-reported alongside console data.
From user signal to spin-off product: MeetRoll
The product: a Google Meet add-on that gives teachers running online or hybrid classes a reliable attendance record. Found through a real user signal in a monthly check-in call, validated with the tutor, and taken to public distribution.
What changes in the workflow
Observed user workflow · tutor-reported
- 1Start class
- 2Wait ~10 minutes idle wait
- 3Ask a friend or relative to join needs a helper
- 4Screenshot 40+ participants
- 5Share the screenshot
- 6Manually verify attendance manual check
- 1Start class & start add-on
- 2MeetRoll records participants automatic
- 3Attendance is available a record to rely on
Delivery status
- BrainstormGap found with the tutor
- BuildAdd-on implemented
- Tutor demoDemonstrated the solution
- Google OAuthThird-party Safety Team demo
- Marketplace reviewApproved by Google Workspace Marketplace
- PublishedLive on Google Workspace Marketplace
Why publish on the Marketplace as an add-on ?
- No setup for the tutor. A non-technical tutor installs it in one click. No developer mode, test-user lists or config.
- Other teachers get the fix. Anyone running online or hybrid classes on Meet has the same problem.
- One stop solution. Professional tracker under controlled environment
Learnings & Evidence
What held up: Starting with the tutor's story kept the launch scope focused. The Business Profile generated measurable discovery and interactions.
What I'd do differently
Before launch, I should have set up an analytics baseline and tagged each enquiry by source. The enrolment average was tutor-reported, but I had no measured data to compare channels or to show which ones contributed to enrolments.
What to test next
Enquiry volume is measured today. Next, I will track enquiry-to-enrolment conversion, especially for non-local and international leads, track reviews alongside enquiries, and measure how useful MeetRoll is in terms of optimization and organisation.
Evidence
- Live websiteHosted on GoDaddy Open site
- MeetRollGoogle Meet attendance add-on · Published on Google Workspace Marketplace View MeetRoll
All analytics reflect data compiled as of 28 September 2026. Enrolment figures, the earlier average of about 145 and the ~40% increase are approximate and tutor-reported; they may represent one or several grades or batches, and no breakdown by grade or session was provided due to privacy considerations. Search Console and Business Profile figures cover February to September 2026.