Pipeline CRM
Deal stages, forecasting and activity history for a sales team that has outgrown a spreadsheet.
Next.js · TypeScript · PostgreSQL · Tailwind
Explore
From $549
OverviewMarketer1 / 6
CRM & SalesMarketingLive
Marketing Campaigns
Marketing tools are easy to buy and hard to leave, because your contact list and its consent history live in someone else's database. This build keeps both in yours.
- From
- $679
- Function
- 22
- Roles
- 3
- Users
- Unlimited
Next.js · TypeScript · PostgreSQL · Recharts
Inside the app
What it does out of the box
22 connected functions on one schema, spanning three permission levels. Everything below is in the template before a line of customisation.
Dashboard for Elena
The autumn campaign sent to 18,400 contacts yesterday and 2 segments need a consent review.
Campaigns
What was sent, to whom, and what came back.
Segments
Who a campaign goes to, and whether you are allowed to send to them.
Contacts
One record per person, with the consent history attached to it.
Performance
What campaigns produced, beyond opens.
Lead scoring
What a score is made of, so sales can argue with it usefully.
Consent and sending
Lawful basis per contact, and the sending setup that keeps mail delivered.
Audit log
Every send, suppression and consent change. Retained for seven years.
Permissions
Three roles, one build
A marketer builds and sends. A manager owns attribution and scoring. An administrator owns consent policy, which is the part that decides whether you may send at all, and is therefore not a marketer's decision to make.
Marketer7 functions
Build, segment and send
- Build campaigns and reusable segments
- See mailable counts before scheduling
- Track opens, clicks and opt-outs
- Cannot send to a segment without a lawful basis
- Cannot override a suppression
Marketing Manager14 functions
What it actually produced
- Everything a marketer can do
- Leads, opportunities and attributed pipeline
- Cost per lead by campaign
- Tune the lead scoring model
- See which campaigns are habit rather than value
Administrator22 functions
Whether you may send at all
- Everything a manager can do
- Record and evidence consent bases
- Manage suppression and erasure requests
- Configure sending domains
- Read and export the audit log
The build
Every function in the box
22 functions, all of them live in the preview. Nothing on this list is a mockup or a roadmap item.
Access
- Sign in
Campaigns
- Overview
- Campaigns
- Segments
- Contacts
Analysis
- Performance
- Lead scoring
Administration
- Consent and sending
- Audit log
What you get
Delivered as a repository, not a login.
Marketing teams running email and lead nurture against a list of 1,000 to 500,000 contacts.
- 9 production functions spanning three permission levels
- Full source code and PostgreSQL schema in your repository
- Role-based access control, enforced server-side
- Immutable audit log written on every change
- Responsive layouts, usable on a phone, not just resized
- CSV import and export on every core record
- Deployment configuration for your cloud account
- Twelve months of updates, and no per-seat charge ever
Access and evidence
Consent as a record, not a checkbox
The hard question is never whether someone is on your list, it is whether you can show how they got there. Owning the contact database is the point: your list and its consent history stay in your infrastructure.
- Timestamp, source and form content stored at the moment of opt-in
- An import cannot set a consent basis, it must be evidenced
- A segment with no lawful basis recorded cannot be sent to
- Unsubscribes are permanent, global, and survive re-import
- Contacts without a basis are suppressed rather than deleted
- Export and erasure requests are actioned and logged
- Suppression lists are never overwritten by a bulk update
Related
Apps that pair with this one
Community Hub
Spaces, posts and a question-and-answer board with reputation, saved items and a moderation queue that records every decision.
Next.js · TypeScript · PostgreSQL · MDX
Explore From $529
Customer Success Hub
Health scores, renewal calendars and QBR prep for the team that keeps revenue from leaking.
Next.js · TypeScript · PostgreSQL · Recharts
Explore
From $649
Questions
Marketing Campaigns, in practical terms
Do I get the source code for Marketing Campaigns?
Yes, and here it matters more than usual: your contact list and its consent history are the asset most marketing platforms hold hostage. On delivery both live in your database, under your control.
Does this make us GDPR compliant?
No. It gives you the mechanisms compliance depends on, evidenced consent, lawful basis per contact, permanent suppression, and export and erasure on request. Whether you are compliant depends on your policies, your privacy notice and how you actually operate. We scope the specific controls your regulator expects as part of a fitted build.
Does it send the email itself?
It composes, segments, schedules and records. Actual delivery goes through a sending provider, which is a standard integration in a fitted build. You keep your own sending reputation and your own rates rather than inheriting a shared pool.
What happens to contacts we imported without consent?
They are suppressed, not deleted, and cannot be sent to until a basis is recorded and evidenced. Keeping the record rather than quietly removing it is deliberate: if you are ever asked what happened to a list, you can answer.
Can Marketing Campaigns be changed to match how we work?
That is the usual route. A fitted build sets up your segments, scoring model, email templates, sending domains, consent wording, CRM sync, branding and up to two integrations, and typically takes one to three weeks from a signed scope.
What does it cost to run?
Hosting only, paid to your own cloud provider, roughly $50 to $200 a month, plus whatever your sending provider charges per email, which you pay them directly.
Want Marketing Campaigns shaped around your process?
A fitted build adjusts fields, stages, roles and integrations to how your team already works. One scoping call, a fixed price, one to three weeks.
