trackad.ai
the door is data moat weakness — they sell a proprietary-sounding IA but rely on generic integration and first-party data that is portable, so switching is mostly about onboarding rather than impossible.
where the walls are.
no regulatory wall — SOC 2 doesn't count.
the technical wall is real — research-grade engineering, not a weekend.
why this scorehigh confidenceLow non-software spend and no indication of heavy compliance or proprietary infra; enterprise services could raise...
Low non-software spend and no indication of heavy compliance or proprietary infra; enterprise services could raise costs but not evident.
- Site emphasizes connectors and onboarding rather than proprietary hardware or payments handling
- Pricing gated as enterprise/demo suggesting sales motion but no mention of compliance teams or expensive infra
- Estimated competing cost shows low infra spend (~$9 + usage) for an indie replicate
why this scoremedium confidenceIntegration and reliable event reconciliation require engineering effort but rely on standard APIs and common ETL...
Integration and reliable event reconciliation require engineering effort but rely on standard APIs and common ETL patterns rather than deep proprietary tech.
- Connectors are standard APIs (GA, FB, Ads) and periodic pulls are straightforward
- Challenges list includes medium difficulty for event reconciliation and CSV ingestion indicating engineering work
- Proposed stack uses common components (Supabase, Airbyte/Airflow-lite)
why this scorehigh confidenceNo evidence of marketplace, UGC, social graph, or multi-sided liquidity—product is single-sided attribution SaaS.
No evidence of marketplace, UGC, social graph, or multi-sided liquidity—product is single-sided attribution SaaS.
- Report lists no network effects or partner/app ecosystem
- Site focuses on connecting data sources rather than creating marketplace or UGC
- Deterministic distribution signals show no knowledge graph or organic dominance
why this scoremedium confidenceCustomer data and mappings create onboarding friction, but data sources are portable and exports expected, so...
Customer data and mappings create onboarding friction, but data sources are portable and exports expected, so migration is painful but not prohibitive.
- Take_sub notes customers expect exports and reporting, making data portable
- Challenges highlight custom offline/CRM ingestion and onboarding as medium-to-hard friction
- Wedge thesis states switching is mostly about onboarding rather than impossible
why this scorehigh confidenceNo sign of proprietary non-exportable corpus or unique behavioral datasets; model branding (NOA) appears...
No sign of proprietary non-exportable corpus or unique behavioral datasets; model branding (NOA) appears marketing-led over proprietary training data.
- They brand an attribution model (NOA) but core value is unified data and rules, which are replicable
- Sources are first-party APIs and CSVs that customers can export
- Report explicitly states door is data moat weakness
why this scorehigh confidenceNo regulatory licenses or duties mentioned; SOC 2 alone not present and would be low.
No regulatory licenses or duties mentioned; SOC 2 alone not present and would be low.
- No mention of HIPAA, FINRA, KYC/AML, money transmission, or clinical obligations
- Product deals with marketing analytics and standard ad/analytics APIs
- Deterministic signals and site copy do not cite compliance or regulated status
the blunt take.
“They've built a polished attribution wrapper and branded their model NOA — but the core value is unified data and rules, which an indie can replicate by wiring sources and simple models; the real defence is customer success and integrations, not secret algorithms.”
Their site emphasizes connecting media platforms, web/app analytics and CRM data — those sources are standard APIs and CSVs, and customers expect exports and reporting, so a competitor that matches key connectors and offers lower friction onboarding can peel customers off.