PaceCRM website plan

pacecrm.io, 6 pages plus a tutorials library, managed by Marathon Creative. Review the cards, answer the decisions at the bottom, send it back.

0 of 0 reviewed

What the site looks like

Primary nav
Home /What it is, 12 capabilities, pricing teaser, demo CTA
What it does /featuresThe 12 capabilities in depth
Pricing /pricingSeat calculator, what is included, FAQ
Tutorials /tutorialsSearchable how-to library by module
Book a demo /demoCalendar booking, lands in Pace
Under tutorials
/tutorials/getting-startedLogin, mobile app, your first contact
/tutorials/inboxConversations, templates, missed call text back
/tutorials/pipelinesStages, moving deals, opportunity fields
/tutorials/calendarsAvailability, booking links, reminders
/tutorials/automationWorkflows, follow up, internal alerts
plus 7 more module foldersForms, campaigns, reviews, payments, phone, reporting, AI
Footer only
/privacyRequired before any SMS registration
/termsSame, plus seat and billing terms
/404Real 404, not a silent homepage

Pricing as it would appear

$150 first seat, then $100 per additional seat

Live calculator on the page: 1 seat $150, 3 seats $350, 5 seats $550, 10 seats $1,050. Per month, month to month, one seat equals one user login.

SeatsMonthlyPer seat
1$150$150
2$250$125
3$350$117
5$550$110
10$1,050$105

Two things the page has to say and I need your numbers for: build out (the pipelines, fields, workflows, calendars and migration, quoted per account) and usage (texts, emails, calls, billed monthly on actual usage at standard platform rates). Both are decisions D3 and D4 below. I will not publish a usage rate or a build out number you have not given me.

Page by page

Build, hosting and the DNS problem

pacecrm.io is live on GoDaddy DNS right now, with www pointed at flash.funnels.msgsndr.com (a GoHighLevel funnel) and GoDaddy email on the domain (MX at secureserver.net, SPF include:secureserver.net). Cloudflare Pages cannot serve a bare apex unless the zone moves onto Cloudflare nameservers, and moving nameservers carries that email with it, so MX, SPF and any DKIM have to be recreated before the switch or mail stops. That is decision D1 and it is the one that blocks the build starting.

Rollout

Decisions I need from you

0 of 0 reviewed