A MarTech SaaS for enterprise marketing teams, live in 11 months
Source.app's customers reconciled six marketing platforms by hand and reached contradictory answers about the same campaigns. Twistag opened with six weeks of feasibility work on the data model and integrations, then built one normalised event layer, separate views for executives and campaign managers, and an AI analyst that flags anomalies. The MVP went live in eleven months, with no architectural changes mid-build.
- 11 monthsconcept to production MVP
- 6marketing platforms integrated
- Livewith early enterprise adopters
- Client
- Source.app
- Industry
- Software & platforms
- Practices
- Data & Cloud, Product Engineering
- Timeline
- 11 months
- Stack
- React, Next.js, AWS
Six platforms, six versions of the truth.
Twistag built Source.app, a marketing attribution platform that unifies data from six marketing platforms into a single source of truth, from concept to production MVP in eleven months. Source.app's founders had watched customers reconcile Google Ads, Meta, HubSpot, Google Analytics, Search Console and Mailchimp by hand and reach contradictory conclusions about the same campaigns. Twistag opened with a six-week technical feasibility phase — validating the data model, integration strategy and event schema before committing engineering — then built separate executive and campaign-manager views on a normalised event architecture, with an AI Analyst layer that flags anomalies proactively.
Marketing leaders face a fragmentation problem that compounds as their tech stack grows. A campaign manager might check Google Ads for search performance, Meta for social ROI, HubSpot for pipeline impact, Google Analytics for site traffic and Search Console for visibility, and still have no coherent narrative of what is working — because each platform counts differently and the numbers contradict each other. The cost is hours lost to manual reconciliation and decisions made on incomplete data. Source.app's founders saw the pattern across their customer base and decided to build the unified layer. The hard part was designing a data model and an interface fast enough to validate the idea before market momentum moved.
Feasibility first, then the build.
Six weeks of feasibility.
Before heavy engineering, Twistag validated the data architecture, the integration strategy and the event model the platform would rely on for years, and settled which data belongs to executives and which to campaign managers.
One event schema.
Google Ads, Meta, HubSpot, Google Analytics, Search Console and Mailchimp each connect through their own authentication and rate limits, normalised into a common schema and refreshed every four hours.
Two audiences, one product.
Executives see ROI across channels; campaign managers work on daily performance, bids and creative. An AI analyst flags significant shifts in a channel's ROI, with context, before anyone asks.
Live in eleven months, on plan.
Source.app shipped its production MVP in November, just under the eleven-month target. The platform is live with early enterprise adopters using it as their primary marketing performance dashboard, and campaign teams report spending less time pulling data across platforms and more on strategy and optimisation. The engagement also validated the delivery method: starting with a feasibility phase meant the engineering phase ran without architectural pivots mid-build. Stated plainly, these are structural and qualitative results — Source.app has not published a client-side revenue, cost or efficiency figure, and this page does not claim one.
Committing to a data model before validating API complexity is how multi-month rebuilds start.
- React
- Next.js
- AWS
Twistag's communication was solid. We had daily stand-ups and a consistent flow of communication. We felt like we had an open and honest dialogue with them. They worked diligently and even overtime to get things done on time.
