Case study 01 — Agtech
Four platforms, one customer journey
- Client
- Agricultural technology manufacturer
- Sector
- Agtech
- Disciplines
- Headless commerce · Integrations · Custom CMS
- Confidentiality
- Name withheld
Context
The situation
The company sells technical agricultural equipment where the right product depends on the buyer's specific operating conditions. Their digital presence had grown one tool at a time, and each addition made the buying path longer. Product information lived in one place, the education that justified the purchase lived in another, and nothing connected a customer's research to the eventual order.
- Platforms consolidated
- 4 → 1
- Configurator
- Spec-driven
- Content sync
- Automated
Challenges
What was in the way
- 01
Four disconnected platforms in a single customer journey, each with its own navigation and visual language
- 02
No centralized product information system, so specifications drifted between Shopify and marketing pages
- 03
Complex product configurations presented as static tables, leaving buyers to work out fit on their own
- 04
Educational video and technical resources scattered across platforms with no relationship to the products they supported
- 05
No line of sight from content engagement to purchase behavior
Approach
What we built and why
Headless commerce architecture
A Next.js storefront against the Shopify back end, so merchandising, routing, and page composition became ours to control while payments, tax, and fulfillment stayed on infrastructure the client already trusted.
LINKS line configurator
A guided tool that takes the buyer's operating specifications and returns the exact product configuration, replacing a compatibility chart the sales team previously walked people through by phone.
Unified content hub
A custom CMS for video, technical resources, and case studies, with a Vimeo sync engine that keeps the library current without anyone re-uploading or re-linking assets.
Integration layer
An Express.js API joining Shopify and HubSpot so a single customer record reflects browsing, configuration, content consumption, and orders in one timeline.
Inside the build
Screens from the platform
Outcomes
What changed
- One platform carrying the entire customer journey from first search to reorder
- Configuration guidance moved from sales calls into the product experience, improving conversion on technical SKUs
- Product and content information managed from a single source of truth
- Marketing and sales working from unified customer records instead of platform-specific fragments
Stack
- Next.js
- Shopify API
- Express.js
- HubSpot
- Vimeo API
- TypeScript
Industries
Next
More work
Next step
Tell us what is not working
A 30-minute call, no deck. We will ask about your systems and constraints, and tell you honestly whether a custom build is the right answer for your situation.