Joshua Parten

Revenue operations portfolio

I build reporting and CRM workflows that help teams explain what changed and decide what to do next. These case studies describe my work and use fictional data to show how it applies.

Start with historical pipeline reconciliation

See how I checked which opportunities belonged in the month-end count. I traced the discrepancy across historical CRM exports and turned the investigation into a monthly check.

Explore the charts

Monthly recurring revenue waterfall
See how each exception changes the close.
Funnel conversion comparison
Compare deal-row counting with lead-level conversion.
Vendor cost crossover
See how costs compare at three adoption levels.

Revenue reporting and controls

Reconciling historical pipeline

Trace an opportunity count back to historical CRM exports and explain the variance.
Leading weekly and monthly revenue reviews

See how a weekly investigation carried through to the month-end close and follow-up decisions.
Reconciling recurring revenue

Use the MRR waterfall to clear exceptions and tie the close to billing.
Reviewing pipeline health

Compare headline pipeline with the deals that pass the weekly evidence checks.

CRM data and workflows

Bringing billing data into the CRM

Follow Stripe and ChartMogul updates into the CRM and see how the team handles stale data.
Resolving lead-routing ownership

Replay a lead that qualifies for both regional and specialist queues.
Standardizing funnel conversion

See how effective dates and the unit of measurement change reported conversion.
Tracing CRM acquisition sources

Compare verified and provisional source assignments.
Running a CRM intake holding pen

Resolve an ambiguous account match before releasing a contact for import.
Planning a CRM cutover

Catch a missing deal-to-account link even when record counts match.

Customer Success and product

Keeping Customer Success informed

Show how engineering resolutions and customer replies reach the team.
Scoping a product proof of concept

Turn a broad support request into a brief with testable acceptance criteria.

Technology decisions and change controls

Modeling vendor costs at scale

Compare two fictional quotes at three adoption levels.
Reviewing an AI-assisted reporting change

See what the team checks before approving a reporting change.