Packaging Line Stoppage Investigation

Situation at a Glance

The line has never run cleanly. That is the most important single fact here. A fault that appears immediately on a new machine and persists for six months is almost never a random mechanical failure — it is a setup, specification, or materials mismatch that was present at commissioning and has never been corrected.

What the Operator Signal Actually Tells You

Operators are pointing at the film. That is a specific, consistent, and therefore credible signal. It should have been acted on immediately; the fact that it was not is an organisational gap, not a technical mystery. The film complaint typically maps to one of four failure modes on a new packaging line:

The fact that stoppages started "right away" strongly favours the first or fourth cause — a specification mismatch baked in at commissioning — rather than a component wearing out.

Root-Cause Investigation: What to Do in the Next 48 Hours

These steps are sequenced by speed and cost — no new equipment or external resource required for the first three.

Step 1 — Pull the film specification (today, ~1 hour)

Get the purchase order or goods-received note for the film stock currently in use. Compare it against:

• The film specification in the OEM machine manual or commissioning document
• The film specification the machine was quoted and configured for

If these don't match, you have your answer. The fix is either to source the correct film or re-parameterise the machine for the film you're actually using. Do not do both simultaneously — change one variable at a time.

Step 2 — Log the next five stoppages in real time (next 1–2 shifts)

Assign one person per shift to record, at the moment of each stoppage:

• Exact time elapsed since last stoppage or last roll change
• What was happening on the line (sealing, feeding, cutting, splicing)
• What the operator physically had to do to restart
• Whether a roll change had occurred in the preceding 5 minutes

Pattern in this log will either confirm film-roll-boundary failures (mechanical) or mid-roll failures (temperature, tracking, or spec).

Step 3 — Check sealing temperature settings against film data sheet (today, ~30 minutes)

Pull the film supplier's data sheet. Find the recommended seal temperature range for that film. Compare it to the current seal bar setting on the machine. A mismatch of even 5–10°C can cause repeated seal failures or film distortion that jams the line.

Step 4 — Engage the OEM (this week)

The machine is six months old. Contact the OEM's technical support and state explicitly:

• Stoppages have occurred from day one
• Operators consistently identify the film path
• You need a commissioning review, not a maintenance visit

Most OEM warranties cover commissioning defects within the first year. Frame it that way. If the OEM set machine parameters at installation without verifying them against your actual film stock, that is a commissioning failure, and they have an obligation to correct it under warranty or service agreement. Request their commissioning sign-off sheet — if one was never completed, that is leverage.

Step 5 — Source a backup film supplier (this week, parallel to above)

If the current film stock turns out to be misspecified, you need a replacement in hand before your 5-week deadline. Identify at least one alternative supplier who can provide film meeting the OEM's stated specification, with samples available for a trial run within 10 days.

5-Week Deadline: Risk and Recovery Math

At 3 hours of downtime per shift, you are currently running at approximately 62% of theoretical capacity (assuming an 8-hour shift). Fixing the root cause — even partially — changes the picture materially:

If the order requires output that the current line cannot deliver even at full capacity in 5 weeks, that is a separate conversation about overtime, second shifts, or co-manufacturing — but that calculation cannot be run until you know what this line actually produces when it runs cleanly. That figure is a gap in the information provided.

The financial case for acting this week is unambiguous. Even if the investigation and OEM call consume 8 hours of management time, recovering 1 hour per shift pays back $900/day. A 10-day delay to investigate costs a further $9,000–$27,000 depending on shift pattern.

Immediate Action Sequence

1. Today: Pull film spec and compare to OEM machine specification. Log the gap if one exists.
2. Today: Check seal temperature settings against film data sheet.
3. This shift: Assign someone to log the next five stoppages in real time.
4. Within 48 hours: Call OEM technical support. Use the word "commissioning" not "breakdown."
5. Within 5 days: Identify and contact an alternative film supplier for samples.
6. Day 7–10: Run a controlled trial with corrected parameters or alternative film; measure stoppage frequency against baseline.
7. Day 10–14: If stoppages persist after film correction, escalate to a full OEM on-site commissioning review under warranty.

What Remains Unknown

Three inputs would sharpen this analysis significantly:

• Shift pattern (1, 2, or 3 shifts/day) — determines total weekly cost and production recovery potential
• Order volume vs. line capacity at full run rate — determines whether fixing the line is sufficient or whether additional capacity is needed
• Whether a commissioning sign-off was ever completed — determines warranty leverage with the OEM

None of these gaps blocks the actions above; they affect the financial sizing and the escalation posture.

Revenue Bleed Diagnosis & Fix Sequence

Handmade Candle Brand — TikTok-Native DTC

The Core Problem in One Sentence

You are paying to generate awareness on a platform that is not converting, while your 35% margin leaves almost no room to absorb a 40% revenue drop or recoup a $20k spend with zero return.

Where the Money Is Actually Going

Based on what you've described, the bleed is happening across three distinct layers simultaneously:

1. Influencer Spend ($20k → $0 return) — Immediate Hemorrhage

This is the most acute single line item. At a 35% margin, you need to generate approximately $57,100 in gross revenue just to break even on that $20k spend. "Zero measurable return" means one of the following is true — and you need to know which:

The $20k is gone. The question is whether you repeat the mistake next quarter. Stop all influencer spend immediately until root cause is confirmed.

2. The 40k Follower Gap — Structural Problem

You have 40,000 followers and falling revenue. This means your TikTok audience is not your customer. Followers on TikTok are entertainment-seekers; buyers are intent-seekers. The gap between "follow" and "purchase" on TikTok is wider than on any other major platform for physical goods unless the path to purchase is frictionless (TikTok Shop, link-in-bio with one tap to checkout, or a flash sale with urgency baked in). Your funnel is almost certainly leaking between the platform and the cart.

3. Margin Compression at 35% — Structural Fragility

At 35% margin:

• Every $1 of revenue lost requires roughly $2.86 of new revenue to replace (because cost base doesn't shrink proportionally).
• A 40% revenue drop does not mean a 40% margin hit — it means fixed costs (labour, materials, packaging, platform fees) are now eating a larger share of a smaller revenue number. Your effective margin right now is likely below 20% or negative.
• You cannot spend your way out of this problem. Any further paid acquisition spend before fixing conversion is cash destruction.

Fix Sequence — In Priority Order

Do these in this order. Each step unlocks the next.

Step 1 (This Week): Stop the Bleed

• Halt all influencer spend. Zero. No exceptions until Step 3 is complete.
• Pull your last 90 days of store analytics and answer: What is your current conversion rate? What is your average order value? What is your cart abandonment rate? If you don't have these numbers, get them from Shopify/WooCommerce/your platform today — they are already there.
• Identify your top 3 selling SKUs. These are your only products that matter right now.

Step 2 (Days 2–7): Diagnose the Funnel

You need one data point above all others: are people landing on your site and not buying, or are they not landing at all?

• If traffic dropped 40% in line with sales: the awareness channel broke. Your TikTok content stopped driving clicks, or the influencers sent no traffic.
• If traffic held but conversion dropped: your site, pricing, or checkout is the problem.
• If traffic and conversion held but average order value dropped: customers are buying less per order — likely a product mix or promotion issue.

Check your analytics platform (Google Analytics 4 or equivalent) for the 90-day traffic trend. This single check determines whether you fix content, fix the site, or fix pricing.

Step 3 (Week 2): Fix the Conversion Path

Regardless of which funnel break you find, these three fixes cost nothing and are universally applicable:

1. TikTok Shop activation — if you are not selling natively inside TikTok, you are asking followers to leave an app they are addicted to. That friction kills conversions. Set up TikTok Shop and tag your top 3 SKUs in every video.
2. Product page audit — load your own product page on a mobile phone. If the add-to-cart button is not visible without scrolling, your price is not justified by visible social proof, or your shipping cost appears only at checkout, fix all three before spending another dollar on traffic.
3. Abandon cart recovery — if you don't have an automated email (or SMS) sequence for abandoned carts, you are leaving roughly 70% of near-buyers on the table. This takes one afternoon to configure on any major e-commerce platform.

Step 4 (Week 3): Reactivate Your Existing Customer Base

Your cheapest possible revenue is from people who already bought from you. Before acquiring a single new customer:

• Email your existing customer list with a reorder incentive (e.g. 15% off for returning customers, expiring in 7 days).
• If your margin allows, offer a bundle of your top 3 SKUs at a slight discount to increase average order value.
• This costs you margin, not cash. At 35% gross margin, a 15% discount still leaves 20% gross — acceptable for a reactivation campaign.

Step 5 (Week 4+): Rebuild Influencer Spend — But Differently

When you return to influencer spend, the rules change:

• Micro-influencers only (10k–50k followers) in the home décor, self-care, or gift-giving niches — not general lifestyle. Audience match is more important than reach.
• Performance-only deals: gifted product + commission on tracked sales (5–15% of sale via unique promo code or affiliate link). No flat fees until you have proof of conversion from a creator.
• Maximum spend: 10% of the prior month's gross revenue. This caps your exposure at a level your margin can absorb.
• Minimum tracking requirement: every campaign gets a UTM link and a unique promo code. If a creator won't accept tracking, don't work with them.

Cash Runway Prioritization

Given that you are burning through runway, the sequence above is also a cash-preservation sequence:

Do not restart paid acquisition spend until your conversion rate is confirmed healthy and your existing customer base has been fully reactivated. Paying to send traffic to a leaking funnel accelerates your runway burn, it does not reverse it.

What This Report Cannot Tell You Without More Data

Two findings would change the recommendations materially:

1. Your current monthly revenue figure — needed to calculate how many months of runway remain and whether Step 4 alone buys enough time.
2. Whether your traffic dropped or held — this is the single most important diagnostic split, and the answer changes whether you fix content or fix conversion first. Pull it from your analytics platform as Step 2 above.

If your runway is under 60 days, skip Steps 2–3 and go directly to Step 4 (existing customer reactivation) in parallel with Step 1. Revenue from people who already trust you is faster than revenue from new acquisition at any funnel stage.

Pricing Decision: Friday Board Recommendation

The Contradiction You Must Resolve First

Before the CFO vs. sales argument can be decided, the math has to be read correctly.

Your stated figures do not reconcile cleanly. 200 customers × $49 = $9,800 MRR. You have reported $60,000 MRR. That implies an average revenue per account of $300 — roughly 6× the $49 list price. This matters enormously: if your actual ARPA is ~$300, you are not competing on the same price axis as a $19/month rival at all. You are selling a higher-commitment product to a different buyer profile, and the three accounts you lost were likely anomalously large anchors pulling the average up.

Assumption used to proceed: The $60k MRR figure is treated as correct. The 200-customer count and $49 price are assumed to reflect a mix of plan tiers, annual contracts billed monthly, or add-ons that inflate ARPA beyond the base price. The analysis below holds regardless — but the board must see the reconciled numbers before Friday, because the right pricing move looks completely different if ARPA is $300 vs. $49.

What the Current Numbers Actually Say

12% monthly churn is the emergency, not the price gap. At this rate, you lose half your customer base in roughly five months. No pricing decision — up or down — fixes a 12% monthly churn. A company cutting from $49 to $19 with 12% monthly churn just loses money faster. A company raising prices with 12% monthly churn accelerates the departure of marginal accounts. Both moves are cosmetic without diagnosing why customers are leaving.

Why the CFO and Sales Are Both Wrong As Stated

The CFO's "raise prices" case rests on the logic that you serve a premium segment willing to pay more. If your ARPA is $300, that may be partially true — but raising list price when churn is 12% monthly signals desperation to the market, removes fence-sitters, and does nothing about the retention problem. The three accounts you just lost did not leave because the price was too low.

The sales team's "cut to $19" case is a race to the floor against a competitor who has already anchored that number. Matching $19 requires roughly 2.6× your current customer count just to hold $60k MRR — from a base that is actively shrinking. It also permanently repositions the brand at the low end, makes the unit economics of your current customer acquisition cost almost certainly negative, and gives away the margin needed to fix the product gaps driving churn.

The Actual Decision: Three Options

Option A — Defend the Premium Tier, Attack Churn Directly (Recommended)

Price: Hold at $49 base / defend current ARPA. Do not raise, do not cut the headline number. Instead:

1. This week: Conduct exit interviews with the three lost accounts. Get the real reason — price is the stated reason in 80% of exits; it is the actual reason in roughly 20%. You need to know if this is a value gap, a feature gap, or a sales execution problem before Friday.
2. This week: Pull churn cohort data. Is the 12% concentrated in accounts under 90 days old (onboarding failure), accounts on the $49 base plan (price-sensitive segment that should never have been sold to), or accounts above $300 ARPA (a product-fit problem at scale)?
3. For the board Friday: Present a 90-day churn reduction target. 12% → 6% monthly doubles your effective customer lifetime from ~8 months to ~17 months. At $300 ARPA, that is the difference between a $2,400 LTV and a $5,100 LTV — it dwarfs any pricing move.
4. Structural price move (30 days): Introduce a $19/month entry tier that is genuinely limited (no API, no integrations, 1 user seat) — not to compete with the $19 rival directly, but to stop losing price-sensitive prospects before they evaluate you, while protecting the premium tier's positioning.

Risk: Board wants a decisive pricing answer; "hold and fix churn" reads as indecision. Frame it correctly: the pricing decision IS the churn decision.

Option B — Controlled Price Reduction to $29

Price: Cut from $49 to $29. This is a meaningful signal without hitting the floor.

• Narrows the gap to the $19 competitor to $10 (from $30), reducing the "obvious" switch narrative.
• Reduces MRR by up to ~$4,000/month on new business if ARPA assumptions hold — manageable if churn improves.
• Does NOT recover the three lost accounts unless you proactively reach back with the new price.
• Still leaves you with a 12% monthly churn problem that will consume the benefit within two months.

Risk: Signals price sensitivity to your installed base, triggering renegotiation requests from existing customers. Must be paired with a churn intervention or it accelerates the revenue decline.

Option C — Raise to $79 (CFO's Direction, Stress-Tested)

Price: Raise to $79. This only works if:

• ARPA is genuinely $300+ (suggesting annual plans or bundles already price the product correctly and $49 is only the floor)
• Churn is concentrated in low-ARPA accounts you are willing to lose
• You have a differentiated feature or outcome that the $19 competitor cannot match and that you can articulate in one sentence

At 12% monthly churn, a price increase will accelerate churn among price-sensitive accounts in months 1–2 before any quality-of-remaining-base benefit materialises. This option is only viable if you simultaneously launch an aggressive retention program and have the runway to absorb 2–3 months of elevated churn.

What to Put in Front of the Board Friday

Immediate Actions Before Friday (Ranked)

1. Today: Reconcile $60k MRR against 200 customers and $49 price — produce the real ARPA breakdown by plan tier.
2. Today/Tomorrow: Get one live call with each of the three churned accounts. One sentence from a churned customer outweighs any internal pricing model.
3. Wednesday: Pull churn cohort segmentation — where in the customer lifecycle is the 12% concentrated?
4. Thursday: Draft two board slides: (a) the churn math showing what churn reduction is worth vs. what a price cut is worth, (b) the recommended tier structure.
5. Friday: Present Option A as the recommendation with Option B as the conservative alternative. Do not present Option C without the churn data to support it.

This analysis treats financial and strategic content as informational; it is not a substitute for advice from your finance or legal counsel on contract and pricing obligations to existing customers.

Engineer Departure + Demo Survival Plan

Situation Assessment

The real risk is not the missing documentation. It is an undocumented system breaking during or before the demo with no one able to fix it. Everything below is sequenced around that failure mode.

You have two overlapping clocks:

• Clock 1 — Knowledge transfer window: 10 working days before the engineer walks out.
• Clock 2 — Demo deadline: ~20 working days total.

These are not the same problem. Treat them separately.

Clock 1: The Next 10 Working Days (While He's Still There)

This window is non-renewable. Every hour spent on anything other than extraction is a permanent loss.

Day 1 — Today

1. Have one conversation with the departing engineer before anything else. The goal is not to guilt him — it is to negotiate. Most engineers who give notice are not hostile; they will do reasonable things if asked directly. Ask him for:

• A written architecture overview (even bullet points — 2 hours of his time).
• A guided walkthrough of the three riskiest or most opaque modules, recorded on Loom or equivalent.
• Agreement to be available for paid consulting after his last day at a rate you set now (e.g. £150–250/hr, 10-hour cap). Lock this in writing today.

2. Identify the demo path. You need to know exactly which features, screens, and data flows will be shown to investors. Write this list down. Everything that touches that path is Priority 1. Everything else is deferrable.

3. Set up a shared doc (Notion, Confluence, Google Doc — anything). Every piece of information extracted this week goes there immediately. Do not let it live in Slack messages or emails.

Days 2–5 — Structured Extraction

Run daily 90-minute sessions with the engineer. You lead; he talks; someone else types or the session is recorded. Cover these in order:

Do not attempt to document the full 40k lines. You do not have time, and you do not need it. You need the demo path documented to a level where you can diagnose and recover from a failure.

Days 6–10 — Validation and Backup Engineer

Validate the runbook yourself. Follow each documented step without asking him. Where you get stuck, that is a gap — fill it while he is still reachable.

Bring in a contractor now, not after he leaves. A senior contractor who overlaps with the departing engineer by even 3–4 days gets 10× more useful context than one who arrives after. Budget for this. Options:

• Toptal, arc.dev, or Lemon.io for vetted senior contractors (typical rate: $100–180/hr).
• Your investor network — ask your existing investors today if they have a technical contact or portfolio CTO who can advise or refer someone.
• A local freelancer who can be on-site is worth a premium right now because questions get answered faster.

What to tell the contractor in the brief: "We need someone to understand an existing Node/[your stack] codebase well enough to keep it running and demo-ready for 3 weeks. The previous engineer will be available for 1 week of overlap. Documentation is being produced now."

Clock 2: The 4-Week Demo Window

Freeze non-demo scope immediately

No new features until after the demo. Tell your team today. The only code changes permitted are:

• Fixes that prevent the demo path from breaking.
• Demo data setup and reset.
• Cosmetic changes explicitly required by the demo script.

Every other ticket is parked. This is not a negotiation — a half-finished feature discovered by an investor is worse than a missing one.

Demo environment isolation

If your platform runs on a shared environment, create a dedicated demo environment this week. Reasons:

• You can seed it with clean, compelling data.
• A developer mistake in a staging environment cannot break the demo.
• You can test the exact demo sequence repeatedly without side effects.

Rehearsal schedule

Demo day failure protocol

Do this before the demo, not on the day:

1. Prepare a pre-recorded backup of the demo (screen recording at peak state). If the live system fails, you pivot to "let me show you the recorded walkthrough" without panic.
2. Assign one person as the technical monitor (watching logs or a simple uptime check) while you present.
3. Keep the demo reset procedure tested and under 5 minutes.

Honest Assessment of Your Situation

What is achievable: A demo-ready system with a documented critical path, a runbook that lets you or a contractor recover from likely failures, and a contractor engaged before the engineer leaves.

What is not achievable in 4 weeks: Full documentation of 40k lines, a meaningful test suite, or a system that is safe to develop new features on at speed. Do not attempt these before the demo — they compete for the same hours.

Biggest single risk: You fail to extract the demo-path runbook before the engineer leaves, something breaks in week 3, and neither you nor the contractor can diagnose it quickly enough. Mitigate this by treating the runbook as the only deliverable that matters this week.

Second risk: You hire a contractor too late (after the engineer leaves). Every day you delay this costs you irreplaceable overlap time.

After the Demo: What to Do Next

This is not the time to plan this in detail, but note it now so it does not get lost:

• Conduct a full codebase audit with the contractor in week 5.
• Begin writing tests for the demo path first — the highest-value, lowest-coverage area.
• Hire a permanent senior engineer with documentation and testing in the job spec. The architecture knowledge the departing engineer held must never be singular again.
• Consider whether the platform's architecture is sound enough to build on, or whether a partial rewrite of the most fragile modules is cheaper than maintaining the current state.

Immediate Actions — in Order

1. Today: Talk to the departing engineer. Negotiate post-departure consulting. Write the demo feature list.
2. Today: Post a contractor brief on Toptal or arc.dev. Email your investors asking for referrals.
3. Tomorrow: Begin the first extraction session. Set up the shared knowledge doc.
4. This week: Create a dedicated demo environment.
5. End of week 1: Validate the runbook yourself. Identify gaps before the engineer leaves.
6. Week 2: Contractor starts. Overlap with departing engineer even for 2–3 days.
7. Week 2: First full demo rehearsal.
8. Week 3: Record the backup demo video.
9. 2 days before demo: Final freeze. No changes.