ChefTec Platform Modernization — Strategic Roadmap

Architecture Decision

Two Separate Streams — By Design

This roadmap is deliberately split into two independent tracks. They run in parallel but don’t depend on each other. Here’s what each stream does, and why coupling them would be a mistake.

Stream A — Data & CRM

Get Customer Data Out

H1 → H2 → H3 · Owner: Vash

● What it touches: Data only. Extracts, transforms, and loads customer records into HubSpot and the 30point data layer.

● Customer impact: None. Customers don’t know this is happening. Nothing about how the app works changes.

● Risk profile: Low. Reading data from the database and importing it into CRM. If something goes wrong, we re-import. No customer-facing systems are touched.

● Speed: Fast. The data pipeline is already built. Import can begin immediately.

● Outcome: The team can see, contact, and manage every customer — weeks from now, not months.

Independent

Stream B — Activation & Platform

Replace How the App Works

H4 · Vash (receiver) + Mitch (sender)

● Two sides: Vash builds the new validation database & API (the receiver). Mitch updates the ChefTec app to call it instead of Calypso (the sender).

● Vash’s side: Investigate Calypso’s activation logic, design the new schema, build the API that answers “is this customer licensed? what features do they have?”

● Mitch’s side: Rewire the Delphi codebase — replace Calypso SQL calls with API calls to the new system. Build in local cache/fallback.

● Risk profile: High on the sender side (customer-facing Delphi changes). Lower on the receiver side (new backend, testable independently).

● Speed: Discovery first, then build both sides, then dual-mode testing, then gradual rollout. Cannot be rushed.

Why This Separation Matters

⏱

Don’t wait for the hard thing

Activation replacement requires months of careful engineering. If CRM depends on it, the team gets nothing until the hardest problem is solved. Decoupling means visibility in weeks.

⚠

Different risk, different pace

Data migration is low-risk, reversible, and invisible to customers. Activation work is high-risk and customer-facing. They need different testing, different rollout strategies, and different owners.

💰

Value delivered continuously

Instead of one big launch months from now, the team sees ROI in stages: CRM visibility first, then engagement tools, then automation — all while the platform work proceeds safely in parallel.

✗ If we coupled them

“We’re rebuilding the platform and migrating data at the same time. The team will get CRM access once the activation rewrite is done and tested.”

Result: Team waits 3+ months for anything. One stream blocks the other. Risk compounds.

✓ With two independent streams

“The team gets CRM visibility this month. Meanwhile, activation modernization is proceeding on its own track with its own testing.”

Result: Value in weeks. Risk isolated. Each stream succeeds or fails independently.

Detail

What Each Horizon Delivers

H1 — Now → Month 1

Customer Visibility

Vash

The team has no way to see their customers. Renewals, contacts, revenue — all locked in SQL tables only engineers can query.

HubSpot becomes the single view of every customer: 523 companies, contacts, subscriptions, and renewal dates — visible, searchable, organized.

Ready to Execute

Success Criteria Any team member can answer “who is this customer, when do they renew, and how much do they pay?” without asking anyone.

H2 — Immediately After H1

Customer Engagement

Vash

The team can see customers (H1) but can’t communicate centrally. Emails from personal inboxes with no tracking. Outreach is ad hoc.

Email templates, conversation tracking, open/click tracking, meeting scheduler — all from HubSpot. Renewal outreach, welcome messages, and check-ins from day one.

Unlocks after H1

Success Criteria Every customer interaction is logged in HubSpot. No outreach disappears into personal inboxes.

H3 — Month 1–3

Operational Intelligence

Vash

Data goes stale the moment something changes. The team has to manually check renewals, filter lists, and remember to send emails.

Automated CSS→HubSpot sync keeps data current. Renewal pipeline with 90/60/30-day stages and automated task assignments. The plays from H2 run themselves.

After H1/H2 validated

Success Criteria Renewals are proactively managed from HubSpot’s pipeline and task queue — not spreadsheets and memory.

H4 — Month 1–3 (Parallel)

Platform Independence

Vash + Mitch

Every app launch hits Calypso — a legacy Delphi system on a VM with no failover. If it’s down, customers cannot use ChefTec.

Vash builds the new validation database & API (receiver). Mitch updates ChefTec to call it (sender). Dual-mode testing, beta rollout, then full migration. Usage data visible for the first time.

Discovery starting now

Success Criteria If Calypso goes down, customers are unaffected. The app launches and activates through the new system.

Architecture — Phase 1

Where the Data Goes Now

In the immediate roadmap (H1–H3), customer data migrates directly from the CSS database into HubSpot. HubSpot is the destination — the team’s CRM, the source of customer records, and where all engagement happens. For activation (H4), the app will call HubSpot’s API to verify licenses.

This gets the team live fast. HubSpot handles CRM, activation, and reporting. It’s a massive upgrade from Calypso — managed infrastructure, 99.99% uptime, real API. But all the data lives inside HubSpot, which means we’re renting, not owning.

Architecture — Evolution

Where This Grows: The 30point Data Layer

As the portfolio grows beyond ChefTec, 30point will need its own data infrastructure — a database and API layer you own. HubSpot stays as the CRM tool the team uses day-to-day, but the source of truth moves to infrastructure you control. This is when you stop renting and start owning.

Phase 2 is when you stop renting and start owning. The data layer gives 30point vendor independence, portfolio-wide analytics across every company, and an activation API you control. HubSpot stays as the team’s CRM — but if you outgrow it, you swap the tool, not the data.

When Does Phase 2 Happen?

Phase 2 isn’t on the immediate roadmap — and it shouldn’t be. You build your own data layer when:

Second acquisition closes

Two companies in HubSpot means you need a unified layer across both

HubSpot limits bite

API rate limits, data model constraints, or reporting gaps make the walls feel close

Capital raise requires it

Investors want portfolio-level metrics that a single CRM can’t produce on its own

Momentum

What's Already Built

Phase 0 (discovery) and Phase 1 (data preparation) are complete. The pipeline from CSS database to HubSpot-ready exports is done.

Customer Data Extraction

523 active customers identified, cleaned, and enriched

Business Logic Layer

Categorization, sizing, regions, lead source — all rules codified

HubSpot Export Files

Companies, contacts, and deals — ready to import

Data Quality Assessment

Coverage gaps documented — quality validated

Multi-Contact Analysis

Accounts with multiple contacts identified for linking

Communication History

Baseline established for future email sync

Data Quality

87%

Phone

72%

Address

95%

Ready to Execute

HubSpot import can begin as soon as tier is confirmed.

End State

What This Enables

Once all four horizons are delivered, the business has the complete customer picture — relationship data, financial data, and product usage data, unified in one system.

Churn Prediction

Declining usage + approaching renewal = at-risk. Both signals visible and triggering automated outreach.

Customer Health Scoring

Renewal proximity, usage frequency, feature adoption, and support history combined into a single score per account.

Revenue Forecasting

Renewal dates, pipeline stages, and usage trends in one system. Data-driven projections instead of gut feel.

Platform for Growth

The architecture is reusable. Future acquisitions onboard into the same system: map data, build integration, connect.

Broader Vision

From One Product to a Portfolio Intelligence Layer

ChefTec is the first company through the playbook. HubSpot gets the team live immediately. But the pattern we’re establishing — extract, enrich, integrate, operate — isn’t ChefTec-specific. It’s the foundation for turning every acquired business into a data-driven, observable operation.

Phase 1 — Now

ChefTec → HubSpot

Data migrates to HubSpot. Team gets CRM visibility, engagement tools, and automated workflows. Activation moves off Calypso. One company, fully operational.

Phase 2 — As portfolio grows

30point Data Layer + HubSpot

When the second acquisition closes, stand up a 30point-owned database. Every company feeds into your data layer. HubSpot syncs from it as the team’s CRM. You own the data, standardize the metrics, and get portfolio-level reporting across every company.

The Repeatable Playbook

Every acquisition follows the same four steps. ChefTec proves the pattern — every company after takes less time.

Map

Extract customer data from legacy systems

Enrich

Categorize, size, score — apply business rules

Integrate

Connect to 30point data layer via API sync

Operate

Workflows, health scores, revenue tracking — live

What This Means for Capital Raising

Investors fund teams that can see their portfolio clearly and operate it systematically. This infrastructure is the difference between “we think our customers are healthy” and “here’s the data.”

Owned

Portfolio-wide customer data in a database you control — not locked inside a vendor. Swap tools without losing data.

Repeatable

Proven integration playbook that accelerates onboarding for every new acquisition — reducing time-to-value

Defensible

Operational infrastructure that compounds with scale — each company added makes the portfolio smarter, not just bigger

ChefTec is the proof of concept.
The 30point data layer is the product.

Every company added inherits the same visibility, automation, and health scoring. HubSpot is the tool on top — the intelligence underneath belongs to 30point.

Risk & Governance

Risks & Decisions

Risks & Mitigations

Risk	Severity	Mitigation
No customer visibility	High	This is happening now — not theoretical. Renewals are being missed, at-risk customers are invisible, and there’s no proactive outreach. H1 is the direct fix and can begin immediately.
Silent churn	High	Without visibility, customers leave and nobody knows until the revenue is gone. Every week without CRM is a week where churn goes undetected. H1+H2 close this gap.
Team adoption	Medium	HubSpot goes unused if onboarding is poor. H1 includes hands-on walkthrough; H2 gives immediate utility — team can email customers day one.
Calypso outage before H4	Medium	High impact if it happens, but low probability — the system has been stable. H4 runs in parallel to close this window, but this is not the urgent driver.
CSS schema changes break sync	Low	Sync script validates schema on each run and alerts on drift before data is affected.
HubSpot API rate limits	Low	523 customers well within HubSpot’s 100 calls/10 sec limit; local caching as safeguard.

Decisions Needed

Decision	Context	Who Decides
HubSpot tier	Free covers H1/H2. Workflows and sequences (H3) require Starter or higher.	Leadership
Sync frequency	15 min gives near-real-time; daily is simpler but stale.	Vash + Product
Activation fallback policy	After H4, if HubSpot is unreachable, how long is the grace period?	Mitch + Product
QuickBooks timing	Financial data connector is scoped but not scheduled. When does QBO become a priority?	Leadership