Projects Live

TerraCore Landing

Landing that communicates TerraCore's value proposition to Colombian agricultural producers, shows the SaaS modules, the cascade integration flow, and the three pricing plans, and directs to platform registration.

By Valentina Ramírez · Updated: June 19, 2026

View live site

Summary

Stack

AstroTailwind CSSSEOA11yGA4Performance

The problem

A SaaS platform without a conversion landing loses organic traffic before the producer even reaches the app: it needs to present the product, modules, and plans on a single screen.

No visible pricing

The agricultural sector distrusts software without pricing. 'Contact us for a quote' creates friction before you even start.

Differential value is invisible

That the modules talk to each other is not obvious. Without demonstrating it before pricing, the landing loses the conversion.

Distrust around data

The producer does not want their costs and production data leaving the farm. Without an explicit privacy section, trust is never earned.

What I built

01
Astro with static output: section components, optimized build, and continuous deployment to Netlify.
02
Vertical conversion flow in 8 sections: Hero, value proposition, 6 modules, cascade integration, field UX, benefits, pricing, and FAQ.
03
Three plans with explicit pricing in COP: Seed ($2.5M/mo, 1 location, 5 users), Professional ($5M/mo, 3 locations, 15 users), and Enterprise (from $10M/mo, unlimited).
04
Dedicated privacy and security section: Ley 1581 de 2012, TLS on endpoints, no data mining, and guaranteed CSV export.
05
No own backend: CTAs point to a demo form and direct WhatsApp channel.
06
Google Analytics (GA4) for behavior tracking: sessions, scroll depth per section, CTA clicks, and traffic source.
07
Full technical SEO: title, meta-description, og:*, twitter:*, canonical, and schema markup.
08
Accessibility (a11y): heading hierarchy, aria-labels, and WCAG AA contrast.
09
Performance: static output, WebP images, and immutable cache on Netlify.
10
Tailwind CSS with light/dark mode.

Six modules

Dashboard, Livestock, Supplies, Tools, Production, and Animal Health. Each with real fields from the farm workflow.

Cascade integration

Visual flow: vaccine applied, supply deducted, booster scheduled, status updated. Demonstrates differential value before pricing.

Field UX

Sidebar with always-clear context, tables with large rows and tabular numbers, critical alerts above generic notifications.

Security and privacy

Dedicated section: Ley 1581, TLS, roles and permissions, CSV export in 48h, and guarantee of no data mining or AI training.

Architecture decisions

1. Copy focused on the pain, not the product

Context: The agricultural producer does not search for 'agro-industrial SaaS'. They search to stop using Excel and notebooks.
Trade-off: Technical copy does not connect with the field. Pain-focused copy does, but requires knowing the real operation.
Decision: Hero with no mention of the stack. 'No Excel. No notebooks. No WhatsApp.' plus a first-week benefit as a concrete promise.

2. Integration before pricing

Context: TerraCore's difference from Excel is that the modules talk to each other. That is not obvious to the producer.
Trade-off: Going straight to pricing before demonstrating differential value lowers conversion.
Decision: Cascade flow section ('If you log a vaccine...') before the pricing table. The user understands the value before seeing the cost.

3. Google Analytics to iterate with real data

Context: Without behavioral metrics, landing design is intuition: you do not know which sections are read, where users drop off, or which CTA converts.
Trade-off: GA adds a third-party script with privacy implications that must be declared in the cookie policy and consent banner.
Decision: Google Analytics with explicit cookie consent. Allows tracking sessions, scroll depth per section, CTA clicks, and traffic source to iterate the design with real data.

4. Dedicated privacy section

Context: Production and cost data are sensitive to the producer. Trust is a blocker.
Trade-off: Omitting it assumes trust. In the agricultural sector, trust must be earned explicitly.
Decision: Complete section with Ley 1581, TLS, roles, CSV export, and guarantee of no data mining or AI training.

Results

Complete conversion flow in 8 sections: from producer pain to demo CTA.
Three plans published with COP pricing, explicit features per plan, and clear VAT and cancellation terms.
Central metric communicated: -42% in administrative time measured in pilot farms.

Learnings

A SaaS landing for a non-technical niche must speak the client's language: every section was written in field vocabulary, not software vocabulary.
Separating the value demonstration (cascade integration) from the pricing section reduces cognitive load: the producer arrives at the plans having already understood what differentiates TerraCore from Excel.

One click away

Your next idea deserves
code that can carry it.

I design and build complete products: from the backend to the interface your users love. With integrated AI and security by design.

Projects from COP 2,000,000 / USD 500 depending on scope (MVP from 3-6 weeks).

Limited availability, I respond within 24h.

Start my project See services