Led by Jessica Lopez  ·  jessica.l.lopez@gmail.com
Austin, TX  ·  Remote

Post-sale infrastructure for early-stage SaaS

Most early-stage SaaS companies don't have a post-sale problem. They have a post-sale absence.

No implementation playbook. No onboarding that scales. No renewal motion that isn't just someone remembering to call.

Built for companies with compliance requirements, ERP integrations, or multi-role deployments — where "figure it out as we go" is an expensive strategy.

Ready to talk? jessica.l.lopez@gmail.com

Most engagements begin with the Post-Sale Diagnostic. Two weeks, flat fee, written findings — so you know exactly what needs to be built before committing to a larger engagement.
Post-Sale Diagnostic

A structured assessment of your full post-sale motion — sales handoff, implementation, onboarding, health visibility, renewal. Delivered as a written findings doc: what's broken, what it's costing you, what to fix first.

Entry point
Fixed fee
2 weeks
Written deliverable
Infrastructure Build

Implementation playbook, onboarding framework, health scoring model, renewal motion — built, documented, and handed over in a form your team can actually run. Not a strategy deck. Operational infrastructure.

Scoped engagement
6–12 weeks
Full documentation
Fractional CS Ops Retainer

Not a consultant you check in with. An operator inside your post-sale function — attending the meetings, owning the outcomes, making the work move. Scoped to specific operational results each quarter, not hours logged. Maximum two clients at any time.

Monthly retainer
Quarter-by-quarter
Outcome-scoped

I'm Jessica Lopez. I built the post-sale function at a workforce time tracking company from scratch — no ops team, no playbook, no template. The product sat at the center of everything downstream: project cost accounting in Dynamics and NetSuite, client billing in Sage Intacct, payroll runs in ADP, resource forecasting in Power BI and Tableau. When time data is wrong, every dashboard that depends on it is wrong. My customers couldn't afford that. Neither could I. Before SaaS, I coordinated construction projects — field payroll, labor compliance, job cost tracking on projects where the margin for error was the same. That background is why I took implementation seriously before it was my job title. Across 274 accounts and six years, I delivered 6.1% churn, $1.4M+ in quantified impact, and $1.1M+ in expansion pipeline. With no dedicated support. That's the work Spillar runs on.

6.1%
Churn rate delivered
$1.4M+
Quantified impact
$1.1M+
Expansion pipeline built
56
ERP-integrated implementations

The right place to start is a conversation.

Start with a diagnostic call → jessica.l.lopez@gmail.com