Rebuilding the four operational systems that are slowing PSNI down — and creating the capacity for the strategic work the team has been wanting to get to.
Four operational systems at PSNI are consuming staff time, fighting growth, or producing data the team can't fully trust — and the strategic work everyone wants to focus on (course redesign, content updates, network growth) keeps getting pushed. This proposal does two things at once: it replaces or automates the manual processes that are absorbing the team's week, and it lays out what each of the four systems can look like once HubSpot's newer toolkit (Data Hub, Content Hub, HubDB, Breeze) is in the picture. The goal is not just to swap tools — it's to create operational capacity so PSNI staff can spend their time on the work only they can do.
Each project tackles a system that's slowing PSNI down today. Tap any card to jump.
Smartsheet at $8K+/yr is at its data limit. Replace it with a HubSpot custom object plus a gated Content Hub portal. Dropdown-forced client names, automatic partner-CSP triggers, native dashboards.
Read more →A single intake form fans out into workflows that drive TalentLMS, ESNet, the master directory, and the principal dashboard. The manual chain disappears.
Read more →Retire Savanta. Use HubSpot's Courses object (activatable now on PSNI's current subscription) as the system of record. Move learning into TalentLMS. ClassMarker for testing, Certifier for badges. One front door for CSPs.
Read more →HubSpot becomes the canonical source. CSPs maintain their own contacts via the portal. The annual chase becomes a quarterly nudge.
Read more →A one-time build, a small ongoing management commitment, and a HubSpot stack change — structured so recurring tool costs come down even while the new platform capability goes up.
| Investment | Type | Cost |
|---|---|---|
| Pivot build — design, build & migrate all four projects | One-time | $5,000 |
| Pivot management — ongoing oversight, tuning & the sync layer | Monthly | 10–20 retainer hrs/mo |
| HubSpot stack — Content Hub Pro + Data Hub Pro + Service Hub Enterprise (1 seat) | Monthly | $1,470$600 /mo* |
| ClassMarker + Certifier — testing & certificates (already in motion on PSNI's side — referenced only) | Monthly | In progress |
*Discounted bundle price, available only in the June pricing window below. List price for all three is $1,470/mo.
PSNI runs on Marketing Hub Pro + Sales Hub Pro today, and HubSpot's Courses object can be activated right now at no extra cost — so the certifications rebuild needs no license change. The new capability comes from three adds: Content Hub Pro ($600/mo list) for the gated CSP portal, Data Hub Pro ($720/mo list) for sync, and Service Hub Enterprise ($150/mo list, 1 seat) for the custom object behind M2M reporting. Bundled at $600/mo if secured in June — see the pricing window above.
Design, build, and migrate all four projects: the M2M custom object and gated portal, the certifications architecture, the onboarding workflow, and the contact-directory cleanup. A single one-time fee of $5,000 covers the work end to end — roughly 3 months parallel or 4–6 months sequential, phased so you can stop at any phase boundary.
Once live, the build is maintained and iterated under your existing Pivot retainer — roughly 10–20 hours per month for oversight, workflow tuning, and the Cloudflare Worker sync layer. No new line item; it draws on retainer time you already have.
One-time: $5,000 to build all four systems. Recurring: $600/mo for the full HubSpot stack if locked in June (vs. $1,470 at list), plus management from existing retainer hours. Against that, recurring costs come out — Smartsheet ($8,000+/yr) eliminated, Savanta retired, and Power BI developer hours optional. Recurring tool spend is roughly flat-to-down from day one, the one-time build is recovered through reclaimed staff time inside the first year, and PSNI lands on a stack that grows with the alliance instead of fighting it.
Your developer's Power BI build doesn't have to go away. HubSpot dashboards will cover most of the M2M reporting needs natively, and Data Hub can push HubSpot data into Power BI if you want both. The decision is whether the dashboards you've already invested in justify the data sync — or whether the native HubSpot reports get you what you need at a lower stack cost.
Retire Smartsheet. Move reporting into HubSpot with a gated portal. Solve the matching problem structurally.
Four moving parts. None requires Smartsheet or developer dependencies.
Stores every M2M project. Source CSP, partner CSP(s), client, value, dates, status, notes. Lives in HubSpot.
Dropdown sourced from HubSpot Companies or a HubDB vocabulary. Free text dies. Matching becomes deterministic.
Each CSP sees only their own projects via Content Hub Memberships. Add, edit, mass-update. Never sees competitors' data.
Source CSP submits → partner CSP gets a pre-filled draft. One-click confirm. The match is structural, not textual.
Service Hub Enterprise unlocks custom objects (the Project object is the foundation of this entire build). Data Hub Pro handles sync. Content Hub Pro provides the gated portal with password protection and dynamic content. Cost of the new HubSpot stack is meaningfully offset by retiring Smartsheet ($8K+ today, plus the second data-tier bill they've quoted). Power BI optional.
Collapse the spreadsheet → directory → HubSpot → TalentLMS → ESNet chain into one form and a workflow.
The onboarding form is the only thing a new CSP touches. Everything else flows from it. No spreadsheet emails.
Principals see playlist-style progress bars inside the portal — the same model they see in HubSpot itself.
The carrot still works. The principal completes the units → ESNet access is granted automatically. You're not in the loop.
With admin lifted, the time exists for the video refresh. Claude drafts script revisions; staff review and hand off.
Same Data Hub and Content Hub investment from Project 1 (no double-counting). Plus a TalentLMS API integration build — Pivot scopes this. ESNet integration depends on what its API exposes; if it's a black box, scheduled CSV export from HubSpot is the fallback.
Retire Savanta. Make HubSpot's Courses object the system of record. Replace open-book PDF tests with real learning.
Released by HubSpot in late 2024, the Courses object is purpose-built for tracking who is enrolled in (and certified by) what training program. Each of PSNI's three certifications becomes its own Course record. The good news: it's available on PSNI's current Marketing Pro + Sales Pro subscription — a Super Admin can activate it today. From that moment, the certification program has a real CRM-level home.
Registered → Test Sent → In Progress → Passed → Certified → Renewal Due. Stage moves drive workflows.
"Show every contact at a CSP certified in Quality." "Who's due for renewal?" Standard reports, no exports.
A stage moves to "Passed" → Certifier fires, ESNet updates, principal is notified. No manual intervention.
Content Hub pages pull live from Courses records. The certified-CSP directory updates itself.
Expiration date as a property. Workflows watch the calendar and fire 90/60/30-day reminders.
Associate Course records to Contacts; reports roll up to the Company. "How many CSPs hold all three?" — answered.
The Courses object is not an LMS — it doesn't host video, render quizzes, or track lesson-by-lesson progress. That's why TalentLMS stays for delivery, and ClassMarker handles testing. Courses is the system of record; the other tools are the delivery surfaces; completion events flow back to advance the Course pipeline. This is the right division of labor — using each tool for what it actually does well. The object is also newer than other HubSpot objects; we'd be deliberate adopters, not bleeding-edge. Pivot scopes the architecture so the work holds up as HubSpot evolves the object.
Each tool does one job well. The Courses object is the spine that ties them — and Pivot builds the integration layer that keeps PSNI's other systems in sync.
Hosts the test bank. Generates and sends links natively. Time limits, randomized questions, auto-retests. Results flow back to HubSpot via Zapier.
On a pass, generates the branded certificate PDF and the LinkedIn-shareable badge automatically. Emails the CSP directly. No staff handling of PDFs, zips, or social kits.
Stays in the picture for content delivery. Each handbook converts to a structured course — modules, units, knowledge checks. Claude does the conversion heavy lift.
The CRM-level system of record. Completion events from TalentLMS and ClassMarker advance Course pipeline stages, which fire downstream workflows.
Off-the-shelf tools cover testing, certificate generation, and CRM tracking. They do not update ESnet or the master directory when a CSP passes — those updates have always required manual staff work. Pivot's Cloudflare Worker closes that gap: triggered by the HubSpot Course stage change, it pushes the new certification status into ESnet and updates the master directory automatically. It's a pattern Pivot uses regularly to connect HubSpot to systems that don't have native integrations.
This is the part of the workflow that has no SaaS solution — and where Pivot's build experience earns its keep.
When a CSP earns a certification, their ESnet profile reflects it within minutes — not when staff get around to updating it. Members see accurate data every time.
The Worker writes back to the master directory (or generates it on demand from HubSpot) so the four-source-of-truth problem stops compounding with every cert awarded.
Same Worker pattern handles the onboarding sync, M2M project sync, and contact directory updates. Build once, apply across Projects 1–4.
The integration code lives in PSNI's Cloudflare account. No third-party middleware subscription. Pivot maintains it under retainer; PSNI can take it in-house any time.
Today's open-book tests measure persistence with Ctrl-F. The new model measures application.
Not just at the end. Force engagement with the material section by section.
CSPs can't memorize last year's questions or screenshot them and pass them around.
30 seconds is enough for someone who studied. Not enough to copy into Claude and wait for an answer.
Test application, not recall. These certifications are about doing the work — the questions should reflect that.
ClassMarker and Certifier are the new third-party tools — both dramatically cheaper than Savanta combined, with no manual work per test or per certificate. The HubSpot Courses object is already available on PSNI's current Marketing Pro + Sales Pro subscription — no license change needed to start the certifications rebuild. TalentLMS stays in the picture for content delivery. Pivot builds the sync layer (Cloudflare Worker) that updates ESnet and the master directory when a certification is earned — the glue no SaaS tool provides.
HubSpot becomes canonical. CSPs maintain their own contacts. The annual chase goes away.
Same Data Hub and Content Hub investment from Projects 1 and 2. The directory work shares infrastructure with the M2M and onboarding builds — once you commit to the gated portal, this becomes additive, not separate.
Even with all four projects implemented, there's a layer of admin work that won't belong in HubSpot workflows. That's where Claude Worker and AskElephant come in — not replacements for the project work, but the layer that handles the residual stuff that's too small to automate formally but too repetitive to keep doing by hand. Anyone on the PSNI team can use these tools.
Once installed, Claude Worker runs on a staff member's desktop on a schedule and handles the admin tasks they'd otherwise do themselves. Concrete things to point it at, ranked by impact:
| Task | What Claude Worker does | Time saved / week |
|---|---|---|
| Email triage & draft replies | On a schedule, reads the inbox, identifies emails needing a response, drafts replies in the user's voice, queues them as Gmail drafts for one-click send. | 3–5 hours |
| M2M reporting reminders | Until the new HubSpot-native flow is live, segments who hasn't reported this month, drafts the reminder email, excludes the people who have, queues it for review. | 1–2 hours |
| Master directory cleanup | Points at SharePoint master and HubSpot contacts. Identifies duplicates, mismatches, missing roles. Produces a checklist or executes with staff sign-off. | Weeks → days |
| Certificate generation (interim) | Until ClassMarker + Certifier go live, generates the certificate PDF, builds the social media zip, queues the email — 30 minutes becomes 30 seconds. | 30 min / pass |
| Course content drafting | Drop a handbook PDF and brand guide. Ask for a TalentLMS-structured outline. Refine through conversation. Days drop to hours. | Days / course |
| File & downloads cleanup | Points at a downloads folder. Organizes by type, removes duplicates, archives anything older than 90 days. Schedule weekly. | 30 min |
Download the Claude desktop app. Open it. Type: "What can Claude Worker do for me?" Then: "Help me set up a scheduled task to organize my downloads folder weekly." Start there. Once a team member has seen it work on something low-stakes, the trust builds and they'll find places to apply it everywhere.
AskElephant is the call notetaker that joined our initial conversation. Pivot is partnered with them and uses it across our own business. The reason it matters for PSNI isn't sales prospecting — it's every other call the team has.
Automatic minutes, action items, decisions — all written back to HubSpot when relevant.
When a CSP calls about onboarding, certifications, or M2M, the call is captured, summarized, action items become tasks — for whichever team member owns the follow-up.
When evaluating ClassMarker or any other tool, the call is captured. Ask Claude later what they said about Zapier integration — it pulls the answer.
"What's every commitment the team has made to a CSP this quarter?" "Summarize the recurring complaints from CSPs about onboarding." Intelligence PSNI doesn't have today.
AskElephant is meaningfully better than HubSpot's native notetaker — we've tested both extensively. It's the tool we use across the Pivot business.
Pivot and AskElephant are partnered — we'd love to walk the PSNI team through the integration live, against PSNI's actual use cases (CSP support calls, internal team meetings, cross-call analysis). No prospecting pitch, just the workflow. One click below and Jane will reach out to coordinate a time.
Three considerations drive sequencing: which projects unblock the others, where the highest pain is, and what order minimizes throwaway work.
PSNI team members install Claude desktop and point Claude Worker at email triage and downloads cleanup. Courses object activated in the existing HubSpot portal (no license change required) — initial Course records built for the three certifications. Savanta-to-ClassMarker scoping starts in parallel. Pivot drafts the HubSpot subscription change proposal (Service Hub Enterprise, Content Hub Pro, Data Hub Pro) for review.
HubSpot subscription updated (Service Hub Enterprise for custom objects, Data Hub Pro for sync, Content Hub Pro for the portal). Project custom object built. Master directory migrated to HubSpot. Roles converted to properties. Gated portal v1 launched with M2M reporting.
HubSpot Courses object activated and pipeline built (one Course record per certification). ClassMarker + Certifier integrated and writing back to Course records. Pivot deploys the Cloudflare Worker sync layer that pushes certification status to ESnet and the master directory on stage change. Savanta workflow retired. First handbook converted to TalentLMS course. Certifier badges issuing automatically.
Single onboarding form replaces the spreadsheet chain. TalentLMS API integration live. Principal dashboard inside the portal. Welcome automation drafts queued for marketing review.
Smartsheet retired. SharePoint master retired or reduced to a generated export. Remaining handbooks converted to TalentLMS courses. AskElephant rolled out across the team.
Phases can overlap. Parallel (different Pivot resources on each track) compresses the first three phases to ~3 months. Sequential is closer to 5 months. The decision depends on Pivot retainer capacity and your appetite for change happening fast.
Full figures are in The Ask above: a one-time $5,000 Pivot build, the HubSpot stack at $600/mo if locked in this June (vs. $1,470 at list), and ongoing management drawn from existing retainer hours. The headline: recurring tool costs go down (Smartsheet $8K+ gone, Savanta gone, Power BI possibly retired) and the one-time build is recovered through reclaimed staff time within the first year.
Framing for leadership conversations and for anyone on the team who needs to take this further internally.
Hard costs out, recovered time in.
Currently $8K+/yr, escalating with usage tier increases. Eliminated.
Replaced by ClassMarker + Certifier at meaningfully lower cost and dramatically less drag.
Conservatively 15–20 hours per week across the team once Phases 1–3 are live. Nearly half a full-time equivalent back, redirected to strategic work.
If native HubSpot dashboards meet the need, developer hours stop. If not, Data Hub keeps Power BI fed automatically.
Beyond the savings, the strategic ground this unlocks.
Every "ask PSNI" interaction becomes a portal interaction. CSPs get faster answers; staff stop being the bottleneck.
Clean client names, structural matching, automatic partner triggers. The numbers PSNI quotes externally become accurate, not approximate.
From PDF-search testing to course-based learning with knowledge checks. Certifications signal actual skill, not effort.
Course redesign, member growth initiatives, deeper TalentLMS use, partnership development. None of this happens while the admin chain consumes the day.
What could go wrong, and how the proposal addresses it.
Phased rollout. PSNI announces each change with the benefit framed (no separate Smartsheet login, mass updates possible, faster certificate turnaround). The new flow is easier than today's — adoption follows.
Data Hub gives PSNI a HubSpot-native path so the Power BI dashboards become nice-to-have, not critical path.
HubSpot Memberships scope visibility per contact and per company. The architecture matches the constraint that ruled out Smartsheet's auto-trigger originally.
Each phase is independently scoped and approved. You can stop after any phase if the value isn't materializing.
PSNI is paying for tools that fight the org's growth (Smartsheet hitting limits, Savanta in decline) while staff spend significant portions of every week on admin work that HubSpot's newer toolkit handles natively. This proposal eliminates the worst tools, redirects spend to a stack that grows with PSNI, and gets the team back to the strategic work the alliance was built for — at a net cost reduction within the first year.
Here's what I'd like to land.
Confirm scope. Anything I've overstated, understated, or missed across the four projects?
Decide parallel vs. sequential. Depends on your appetite and Pivot retainer capacity.
Agree on what to take to leadership first. Full proposal, or a phased ask starting with Phase 0 + Phase 1.
Schedule the HubSpot subscription review. Data Hub and Content Hub need to be in place before Phase 1 starts in earnest.
Pick the first Claude Worker task. The win this week that proves the model.
Answers help us tighten the proposal and surface anything I should know.