Campaign Overview
The traceo.cat landing page is the first public-facing asset in the Linx → Traceo → Baselinx funnel. It positions Traceo as “traceability intelligence for modern teams” and seeds the BASELINX reveal narrative throughout the page without naming Baselinx as a separate product until the pricing section.Positioning Strategy
Hero: “Your requirements are already connected.” — This channels the core BASELINX insight: the traceability graph already exists in your work; Traceo just surfaces it. The headline implies discovery, not creation. Users don’t need to change their process — they need to see what’s already there. Anti-positioning: Every section implicitly positions against IBM DOORS, Jama Connect, and Polarion. Key phrases: “no procurement cycles,” “no six-figure contracts,” “requirements management that engineers choose, not procurement.” The target is the engineer who’s been forced to use DOORS and hates it. Trojan horse feature: Feature card #4 (“Every link is a requirement in disguise”) describes the smo1.io link-to-requirement bridge without using the word Baselinx. Users create short links, Traceo silently builds their traceability graph. This is the bottom-up discovery path from the gist strategy doc.Funnel Architecture
| Stage | Element | Conversion goal |
|---|---|---|
| Awareness | Hero + eyebrow badge | Scroll to features |
| Interest | Features + social proof | Scroll to pricing |
| Desire | Pricing + lifetime deal | Click CTA |
| Action | Waitlist + nav CTA | Email capture or app.traceo.cat signup |
| Retention | Founder story + journal teaser | Emotional investment, follow along |
| Referral | Share CTA + social buttons | Organic word-of-mouth |
Pricing Architecture
| Tier | Price | Purpose |
|---|---|---|
| Starter | Free | Bottom-of-funnel entry, 50 requirements cap creates natural upgrade pressure |
| Pro | $29/mo | Core revenue tier, highlighted as “Most popular” |
| Baselinx Enterprise | $149/mo | Enterprise anchor price, makes Pro feel accessible |
| Founding Member Lifetime | $299 one-time | Urgency driver, limited to 100, funds early development |
Content Trails to Develop
- Founder journal series: The journal teaser CTA is live but links to a placeholder. Priority: publish 3-5 entries covering the spacecraft-to-software arc, auth debugging war stories, and the BASELINX naming decision.
- smo1.io demo: Feature card #4 describes link-to-requirement discovery. A 60-second screen recording of creating smo1.io links and watching the traceability graph assemble would be the single highest-impact content asset.
- “Why we left DOORS” blog post: Target the specific pain points listed in FAQ answer #1. SEO play for “[DOORS alternative]” and “[Jama Connect alternative]” keywords.
- Building in public thread: The open-startup section links to GitHub and the journal. A weekly X/LinkedIn thread showing real metrics (waitlist signups, feature development) feeds the organic discovery loop.
- Testimonial replacement: Current testimonials are placeholders. Priority: get 3 real quotes from beta users within 30 days of launch.
Messaging Bank
Key phrases established on the landing page, ready for reuse across channels:- “See the connections others miss” (tagline)
- “Your requirements are already connected” (hero)
- “The connections were always there. Now you can see them.” (features)
- “Built for builders. Priced for humans.” (pricing)
- “Requirements management that engineers choose, not procurement” (features subhead)
- “Every link is a requirement in disguise” (feature card)
- “Traceability intelligence for modern teams” (meta/footer)