The 12-Month Build: Phasing a Martech Stack from Zero

Marketing Academy · Field Work●Marketing Tools

All projects·From: Building Your Martech Stack

CoreBuild the Asset· 70 minutes

Jyoti CNC Automation

Objective: Given Jyoti CNC Automation's 12-month marketing goals and current zero-tool baseline, apply the lesson's goals-first, phased-build framework to produce a month-by-month stack rollout plan with named tools and integration checkpoints.

You're the newly hired marketing lead at Jyoti CNC Automation, the Rajkot-based machine tool manufacturer that listed on the NSE/BSE in January 2024. Marketing has run entirely on spreadsheets and a shared inbox; you have a 12-month runway and a mandate to build a stack that won't need to be rebuilt in year two.

Start from three stated business goals, map each to a tool category, then phase the build across three quarters instead of buying everything in month one.

Before you start

What you'll need

Free path (everything below is enough to finish)

Google Sheets

FreeBuild the goal map and phased 12-month timeline

Free, no vendor lock-in for the planning step itself

HubSpot Marketing Hub

FreemiumCRM plus automation with native integrations for Phase 1-2

Free tier covers CRM and basic automation, native integrations avoid the CSV-export trap from Step 2

Zapier(optional)

FreemiumAuto-route RFQs from the CRM to regional reps in Phase 2

Free tier covers 100 tasks/month, enough for RFQ routing at this stage

The process

3 steps

Step 01 of 03

Mapping goals to required tool categories before selecting software

The lesson's Step 1 says every goal points to specific tool categories, write the 12-month goals first, then let each one name the layer it needs, never start by browsing software.

Jyoti CNC's three goals: '200 qualified dealer/distributor leads globally', 'cut RFQ response time from 5 days to 1', 'track which trade-show contacts actually convert to orders'. Which tool category does each goal require?

Google Sheets— Build a two-column goal-to-category map.

Procedure

Write each of the 3 goals in its own row
Name the martech layer each goal requires (Layer 1 CRM for lead tracking, Layer 2 automation for RFQ response, Layer 1+6 CRM plus analytics for trade-show attribution)
Flag any goal that needs more than one layer working together

Sample output

Goal to Category Map

1. 200 qualified dealer leads globally -> CRM (Layer 1) to log and score every inbound RFQ
2. Cut RFQ response time 5 days to 1 -> Marketing automation (Layer 2) to auto-route RFQs to the right regional rep
3. Track trade-show-to-order conversion -> CRM (Layer 1) + Analytics (Layer 6), needs both connected

Healthy

Every goal names at least one concrete tool category before any vendor gets evaluated.

Unhealthy

Shopping for 'the best CRM' before writing down what it needs to do.

What this means

Goal 3 is the one to watch, it needs two layers talking to each other, which becomes the integration test in Step 2.

So what do I do about it?

Symptom	Action	Effort
Team wants to demo tools before goals are written down	Block vendor demos until the goal-to-category map is signed off	30 min

YouYou can do this yourself, no engineering access required.

Step 02 of 03

Prioritizing integration over standalone features when choosing tools

The lesson's Step 3 says when choosing between two tools with similar features, pick the one with the native integration, a tool with fewer features but clean data sync beats a feature-rich tool needing manual exports.

Two CRM finalists: Tool A has more reporting widgets but only CSV export; Tool B has fewer built-in reports but a native two-way sync with the automation platform you already shortlisted. Which one wins the goal-3 attribution requirement from Step 1?

HubSpot Marketing Hub— Compare each CRM finalist's integration docs against the automation tool's native-integration list before scoring features.

Procedure

Pull each CRM's official integration/app-marketplace page
Confirm whether the automation tool appears as a native (not CSV-based) integration
Score Tool B higher despite fewer built-in reports, since native sync directly serves the Step 1 trade-show attribution goal

Sample output

CRM Shortlist Scorecard

Tool A: 12 built-in report types, export = manual CSV only
Tool B: 6 built-in report types, native two-way sync with HubSpot Marketing Hub automation

Winner: Tool B. Manual CSV exports would break the trade-show-to-order tracking goal within a month.

Healthy

The tool with weaker standalone features but real-time native sync wins the integration-dependent goal.

Unhealthy

Picking the tool with the longest feature list and discovering the CSV export gap only after go-live.

What this means

Feature checklists optimize for the demo, integration checks optimize for month three when someone actually needs the combined report.

So what do I do about it?

Symptom	Action	Effort
Two tools score similarly on features alone	Re-score using native integration with your other confirmed tools as a tiebreaker	30 min

YouYou can do this yourself, no engineering access required.

Step 03 of 03

Phasing a stack build over 12 months by data maturity

The lesson's Step 4 phases the build: months 1-3 get CRM plus web analytics plus one email tool talking to each other, months 4-6 add SEO and social scheduling, months 7-12 add automation and consider a CDP once data volume justifies it.

Jyoti CNC wants all three goals solved by month 2. Using the lesson's phasing, which pieces can honestly ship by month 3, and which have to wait?

Google Sheets— Lay out a 3-phase timeline row per quarter.

Procedure

Phase 1 (months 1-3): CRM (Tool B) + GA4 + one email tool, get these three talking first
Phase 2 (months 4-6): add Zapier to auto-route RFQs between the CRM and the regional reps' inboxes, solving the response-time goal
Phase 3 (months 7-12): add the trade-show attribution reporting once 6 months of CRM data exists to attribute against

Sample output

12-Month Phased Build

Phase 1 (Mo 1-3): CRM + GA4 + Brevo email, connected
Phase 2 (Mo 4-6): + Zapier RFQ routing (solves the 1-day response goal)
Phase 3 (Mo 7-12): + trade-show attribution reporting once CRM has 6 months of deal data

Healthy

Each phase only adds tools once the prior phase's tools are actually connected and in use.

Unhealthy

Buying all 3 tool categories in month 1 and spending the rest of the year trying to get them talking to each other.

What this means

The attribution goal looks urgent but is structurally a month-9 goal, it needs data that doesn't exist yet in month 1.

So what do I do about it?

Symptom	Action	Effort
Leadership wants every goal solved by month 2	Show which goals are data-dependent and can't be pulled forward, present the phased plan instead	half day

EitherYou or a developer can handle this, depending on your access.

Final deliverable

A 3-phase, 12-month martech rollout plan with named tools per phase, integration checkpoints, and which business goal each phase unlocks.

See a reference example

Sample output

Concord Biotech, Year-1 Martech Rollout (excerpt)

Phase 1 (Mo 1-3): Salesforce Essentials + GA4 + Brevo, CRM and analytics connected first
Phase 2 (Mo 4-6): + Semrush for export-market SEO, + Buffer for LinkedIn distributor updates
Phase 3 (Mo 7-12): + Segment CDP once contact volume passes 5,000, attribution reporting goes live

Success criteria

You're done when you can:

Maps all 3 stated goals to a specific tool category before naming any vendor
Chooses the integration-native tool over the feature-richer one where the two conflict
Produces a 3-phase timeline where later phases depend on data/tools established in earlier phases
Free-tier tools alone would deliver Phase 1 and Phase 2