Penguin Strategies · Monthly

What a month with Penguin looks like

A named team, a service level in writing, and one outcome shipping at a time. Priced as a plan, not a bank of time. Here's exactly what's in it.

Outcomes Plan$8,250/ month
$6,000 / month for each additional workstream running in parallel
Three-month minimum, then month to month · USD · Net 30
See how a month runs Talk to Perry

You buy outcomes. We own the delivery.

Most agencies sell you a bank of time and hope it covers the month. We don't, and the difference shows up on the first invoice.

The time-bank model

  • You buy a bucket and hope it covers the month
  • Every request from every stakeholder eats the same budget
  • Scope creep shows up as an overage, after the fact
  • Nobody can say what was delivered, only what was spent

The Outcomes Plan

  • A named set of deliverables each month, with a service level attached
  • One workstream in flight at a time: finish it, ship it, the next starts
  • Anything bigger is priced as an outcome with a date, before work starts
  • Month to month after three. No time in the terms

How a month runs

Four moving parts. Each has a clear boundary, so you always know which one a request falls into and what it costs.

01

Service level

Everything that keeps HubSpot working without changing how it works: break-fix, user questions, provisioning new hires, lead uploads, sequence enrollment, list and view requests, dashboard fixes, permissions.

1 business dayresponse, during your business day
02

Workstreams

One named outcome in flight at a time, rolling. A pipeline rebuilt, a lead-scoring model, a new dashboard set. Finish, ship, next. It's a queue: you own the order, we own the pace.

1 in flightincluded · +$6,000/mo per extra in parallel
03

Projects

Anything that changes how the system works and is bigger than a workstream. Scoped and priced as an outcome, with a date, before anyone builds. No surprise overages.

Priced firstsee the pricing page
04

Quarterly review

What shipped, what it changed in the numbers, what's next. Sat down with whoever owns revenue on your side, so the plan follows the business and not the other way round.

Every quarterplus a weekly sync and a shared board

Covered every month, and where the line is

The whole model rests on one boundary being clear. Here it is.

Covered every month

  • Lead uploads, sequence enrollment, list and view requests
  • User provisioning, permissions, new-hire HubSpot setup
  • Routing, ownership and workflow break-fix
  • Report and dashboard fixes; quarter-rollover checks
  • Weekly sync, shared board, one-business-day response
  • One workstream in flight at all times

It becomes a project when

  • A new tool enters the stack: Clay, Chili Piper, DocuSign
  • A new integration or API contract is designed
  • A new object, pipeline or module is built from scratch
  • Data moves in bulk: backfills, migrations, mass cleanup

Projects get a scope, a date and a price before anyone builds. Most of them are on the pricing page already.

Who's on your account

Named people, not a queue. The same faces every month, and they already know your portal.

Point of contact

Your single front door for requests, priorities and the weekly sync. US-based, on your business day.

Solution architect

Owns the HubSpot data model, every integration contract, and every API path in and out.

HubSpot expert

The consultant who builds and maintains your workflows, objects and reporting. Stays on the account.

Specialists as needed

Clay, integrations, AI agents. Pulled in for the workstream that needs them, then out again.

$8,250 / moOutcomes Plan: service level, one rolling workstream, weekly sync, quarterly review
+$6,000 / moEach additional workstream running in parallel
3 monthsMinimum term, then month to month
USD · Net 30Invoiced monthly at the start of the cycle

If your procurement team needs a time figure to file, it goes in a non-binding appendix. It never appears in the commercial terms, because it isn't what you're buying.

The questions people ask

What if we have two urgent things at once?

You reorder the queue. The workstream in flight finishes, and the next one starts the moment it ships. If two genuinely need to run at the same time, a second parallel workstream is $6,000 a month for as long as you need it.

What happens to a request that's bigger than a workstream?

It becomes a project. We scope it, put a date and a price on it, and you say yes or no before anything is built. Most of the common ones are already priced on the pricing page.

Is there a cap on service-level requests?

No volume cap. The boundary is what's in scope, not how much of it. If a request would change how the system works, it moves to the workstream queue. Everything else gets handled.

Can we start with a project and add the plan later?

Yes, and most clients do. A migration or an AI-readiness build finishes with hypercare; the Outcomes Plan is what keeps it clean afterwards. You decide at the end of hypercare, not at the start.

What if we want to stop?

After the first three months, thirty days' notice. You own the configured portal, the documentation and everything built. Nothing is held back.

Know what a month costs before you say yes

The plan is on this page. What a project costs is on the pricing page. What the call is for is deciding which you need first.

Talk to Perry See project pricing