PeakOne Digital
proposal · managed services · vitamin health
managed services and growth partnership · six-month term

The platform is built. Now it goes to work.

Three connected production systems kept healthy. Your team's requests absorbed. Attention turned back toward growing the business the platform was built to serve, under one monthly engagement.

prepared for
Vitamin Health
prepared by
PeakOne Digital
date
valid
30 days
$6,000
per month · all three programs, one invoice
3
production systems · one accountable team
6
month term · no auto-renew
included monthly capacity
20
delivery credits
included each month
what they cover
Approved enhancements, investigations, automations, operational improvements, and support activity beyond baseline platform operations.
the rate
Most requests consume 1 credit per hour of estimated effort.
expedited work
Priorities pulled forward may require additional credits.
rollover
Unused credits do not roll forward into the next month.
01 · scope

What we operate

Not three products with three vendors. A change in one moves through the others, so we run them as one system.

erp
Odoo 18

Self-hosted. B2B order flow and EDI trading partner traffic via SPS Commerce.

storefront
WooCommerce

Direct-to-consumer site, in two-way sync with the ERP.

call center
Custom web application

The order desk your agents work phone orders in. Purpose-built, and it reads and writes live to the ERP.

02 · coverage

A stalled sync, an admin session nobody expected, an order pattern that does not look like your customers. None of it announces itself, and none of it is caught by looking harder. So the watching is automated.

Instrumentation, alerting, and automated checks across all three systems, running whether or not anyone is at a desk. This is the mechanism behind every commitment in this proposal.

order integrity

Card testing and fraudulent orders read as ordinary traffic right up until the chargebacks arrive, weeks later, after the goods have shipped.

Monitoring sits on the order flow itself. Unusual patterns surface while they are happening, not in a reconciliation at the end of the month.

hosting and access

A storefront can look perfectly healthy from the outside for exactly as long as nobody is checking the inside.

Access is inventoried, patching runs on a cadence, certificates are tracked, and an unexpected admin session raises an alert.

pipeline health

A sync that stops rarely fails loudly. It simply goes quiet, and the gap is found later, in inventory or in a trading partner's exception report.

The storefront sync and the SPS Commerce EDI pipelines report their own health, so a stall reaches us as a notification rather than a discovery.

03 · inclusions

One operational partner, three areas of responsibility

a
Platform operations
  • Monitoring and alerting across Website, ERP, and Integration
  • Backup management with quarterly recovery testing
  • Security patching and dependency management
  • Odoo, WooCommerce, plugin, and infrastructure maintenance
  • SSL, domain, and certificate management
  • SPS Commerce and integration health monitoring
  • 2 staging environments included in the stack
  • Production deployment management
  • Email deliverability and authentication (AWS SES)
outcome

Vitamin Health has a single accountable partner responsible for platform stability, maintenance, monitoring, and recovery readiness.

b
Operational support

Structured support with visibility and accountability.

included
  • Dedicated owner assigned to every request
  • Unlimited ticket submission through the support portal
  • Automated request validation and triage
  • Shared prioritized backlog
  • Written assessment before work begins
  • Start and completion targets on approved work
  • Monthly backlog and roadmap review
  • 20 credits per month · a credit buys an hour of work, or the premium on a faster answer
outcome

Every request has a clear status, priority, owner, and path forward. No more uncertainty about:

  • Who is working it
  • When work will begin
c
Growth and optimization

Five places we already see room to move. Each is a proposal rather than a promise: we test it, report what it did, and retire it if it does not earn its place.

01 · lifecycle email
Earn the second order
  • Abandoned cart, abandoned browse, post-purchase, and win-back flows
  • Segmented against real order history in Odoo rather than guessed
  • Sent through the AWS SES setup we already maintain, so deliverability stays in one place
02 · cart and checkout
Test the path to purchase
  • Structured tests on cart, checkout, and product detail, one variable at a time
  • Variants built and shipped by the team that already runs the storefront
  • Every test written up, including the ones that lose
03 · measurement
See where the drop-off happens
  • Funnel instrumentation across the storefront so every step is countable
  • Session review and heat mapping on the pages that underperform
  • One agreed definition of each number, so nobody is arguing with the dashboard
04 · paid media
Spend against what the data shows
  • Campaign management on the channels that fit the catalog, not all of them at once
  • Creative and landing pages tested against the same funnel definitions above
  • Partly funded by the monthly co-investment set out under investment
05 · reporting
A monthly record, not a highlight reel
  • What shipped, what it moved, and what comes next
  • Losses reported in the same detail as wins
  • Walked through live in the monthly session rather than emailed and forgotten
04 · operating model

Two questions, not one

How fast you need an answer and how fast you need the work are different questions, and most requests only need the first one answered quickly. Every ticket asks both, separately.

field one · response
How soon do you need to know what this is?
Answered with a diagnosis, a working estimate, and a projected start and finish window. Your answer here selects the tier a request is grouped under, and that tier sets the multiplier applied to the credits the work itself consumes.
field two · execution
Where should this sit in the work order?
Urgent, high, medium, or low. This sets sequence against everything else in the queue, and it costs nothing.
response tiers
A daily cutoff, the way a carrier has one. Filed before 2:00 PM Central, the answer lands the same day. Filed after it, the answer lands by 12:00 PM the next morning. Either way you are never waiting more than one business day to know what you are dealing with.
urgent
Same day
Before the 2:00 PM Central cutoff, answered by 5:00 PM that day. After it, answered by 12:00 PM the next business day. Work begins within one business day, displacing scheduled work.
2.0 × credits
expedited
Next day
Answered by 5:00 PM the next business day. Work begins within three business days, scheduled ahead of standard.
1.5 × credits
standard
3 days
Answered by 5:00 PM on the third business day. Work is scheduled in backlog order as capacity allows.
1.0 × credits · no premium
how a request moves
01
You submit. Both fields set, required detail captured at intake.
02
We estimate. Diagnosis, credits required, and a projected start and finish window.
03
You approve. And you may change either priority at that moment, now that you know the cost.
04
We work. Time logs against the estimate on the ticket, visible to you as it goes.
urgency is priced at approval, not at submission
You pay the multiplier for the tier you approve. File something urgent, read the estimate, decide it can wait until next week, and you pay the standard rate on the work.

One exception: a request filed as urgent or expedited and then approved at a lower tier draws a flat one credit for the fast answer itself. Approved at the tier it was filed at, there is no flat charge.
coverage
9:00 AM – 5:00 PM Central, Mon–Fri, excluding holidays. Response measured against covered hours.
the clock
Pauses when blocked outside our control. Reason recorded on the ticket, visible in reporting.
outages
Restoring service is platform operations. Zero draw from the allowance.
the allowance
20 credits per month. A credit buys one working hour, and it is also the unit urgency is priced in. Consumed as work is performed, in half-credit increments, no carry-forward. Overage quoted first, billed at $[overage rate]/hr, never without written approval.
05 · service levels

You will always know where something stands, and what the plan is.

Response and start are commitments. Finish is an estimate. Every ticket carries a projected finish window and a visible time log against it, so progress is a record rather than an assertion. Where work depends on a vendor or platform outside our control, the ticket says so.
A miss gets a written remediation plan. We notify you, explain the cause, and report performance on a regular cadence.
Numeric targets are set at renewal, from measured data. Every response, start, and finish is logged against its estimate from day one. Six months of that record becomes the baseline, and the targets we agree to be held to in the next term.
06 · investment
engagement fee
$6,000
per month · six months

Platform operations, application support, and the growth program in full. Invoiced on the first of the month.

co-investment
$500
per month, funded by us
  • Paid media, testing tools, and experiments, for Vitamin Health specifically
  • Pooled across the term and concentrated where it performs
  • No management percentage charged on media spend
  • You see the plan before we spend it
  • Reported at month three and month six on what it moved, not only what we ran

quoted separately · third-party licensing · hosting beyond current footprint · net-new product development outside the allowance

07 · term

Six months, then a conversation.

The initial term is an evaluation period for both sides, with no auto-renew at the end of it.

Renewal discussions begin in month five, with six months of measured service performance and a written record of what the growth program moved already on the table.

  • Six monthsFrom the effective date. No auto-renew.
  • Month fiveRenewal discussions begin.
  • BridgeWithout a renewal, month to month at the same rate for up to two months, then ends. Either party may end it with written notice.
  • Notice[30 or 60] days written, either party, during the initial term.
08 · acceptance

Start the engagement

Vitamin Health
name and title
date
PeakOne Digital · Christian Chester
signature
date
PeakOne Digital · christian@peakonedigital.com · Dallas, Texas peakonedigital.com · valid 30 days from date of issue