The team you wish you'd hired six months ago.
We embed inside e-commerce and SaaS teams as contractors, consultants, or fractional operators, and get the unglamorous work done. Dashboards that hold up. Ad accounts that stop bleeding money. Systems that don't fall over.
A bench of operators, not a single freelancer. Not an agency of generalists either.
We are not five different vendors in a trenchcoat. We are the same people, every week, inside your ad accounts, your data, your Jira board, actually finishing what we start.— the operating principle behind every engagement
Operators first.
Consultants second.
We've run product, data, and operations inside e-commerce and SaaS companies, not just advised from the outside. Now we bring that hands-on experience to teams that need senior-level execution without a senior-level headcount. You get someone who has actually done the job, not someone who read about it.
Three functions. One team.
Product
We manage the product, not code it ourselves. Roadmaps, specs, and priorities, plus the ad platforms, APIs, and workflow systems it all depends on. If you need hands-on development, we can also stand up and manage a dedicated build team in India.
Data
We turn scattered numbers into dashboards your team actually opens, and analytics that are configured right the first time, so decisions get made on facts instead of guesses.
Operations
We handle the day-to-day that never makes it onto a roadmap: internal tools, ad account troubleshooting, QA, customer issues, and the fires that need someone senior on them fast.
Pick the level of involvement you need.
Senior product leadership without a full-time executive hire. Roadmap, prioritization, and accountability for the team you already have.
Embedded, ongoing part-time capacity. We show up in your tools, on your standups, and in your Slack, like a team member who happens to be part-time.
An advisory engagement. We diagnose what's broken, hand you a plan, and execute alongside your team as much or as little as you need.
Scoped, project-based work with a clear deliverable and a deadline. Good for a single build, a migration, or a fix that needs to happen and stay fixed.
Not sure which one fits? Tell us the problem, we'll tell you the engagement.
Common questions from US e-commerce and SaaS teams.
An e-commerce operator handles the hands-on product, data, and operations work that keeps an online business running: setting product priorities, configuring analytics like GA4, troubleshooting Meta and Google ad accounts, building dashboards, running QA, and resolving customer issues, without needing a full in-house team for each function.
No. We're product managers, not web developers. We manage the roadmap, requirements, and priorities, and configure the ad platforms, analytics, and workflow systems a product depends on. If you need code written, we can stand up and manage a dedicated development team in India on your behalf.
All work is billed hourly. Contractor and consultant engagements carry little to no minimum commitment. More embedded roles, like a fractional employee or fractional CPO, carry a minimum weekly or monthly hour commitment so the engagement can actually move the needle. See the Solutions page for a full breakdown.
Our primary focus is e-commerce and SaaS companies based in the United States. We also take on international engagements on a case-by-case basis.
A fractional CPO owns the product roadmap on an ongoing basis and is accountable for what the team ships. A consultant is brought in to diagnose a specific problem and hand over a plan, with execution support as needed, typically without ongoing accountability for the roadmap.
Have a problem that needs an operator?
Tell us what's broken, slow, or missing. We'll tell you honestly whether we're the right fit.
Everything we run, function by function.
We work across three functions inside e-commerce and SaaS businesses. Most engagements touch more than one of them.
We manage the product. We don't code it ourselves.
We're product managers, not web developers. We set priorities, write specs, and run the roadmap end to end. We configure the ad platforms, analytics, and workflow systems your product depends on. If you need something actually built, we can stand up and manage a dedicated development team in India rather than hand you off to a freelancer marketplace and hope for the best.
Numbers your team can actually trust.
We turn scattered spreadsheets and half-configured tracking into dashboards people open every day. That means clean data pipelines, analytics set up correctly the first time, and KPI frameworks built around the decisions your team actually needs to make, not vanity metrics.
The day-to-day that keeps a business running.
Every growing company has a pile of work that isn't glamorous but can't wait: an ad account quietly losing money, a customer issue queue nobody owns, QA that keeps slipping. We take that pile and clear it, then put a system in place so it doesn't pile back up.
Four ways to work with us.
The right engagement depends on the problem, not the other way around.
Senior product leadership without a full-time executive hire. We own the roadmap, set priorities, and hold the existing team accountable to shipping against it.
Embedded, ongoing part-time capacity for teams that need consistent hands on a function without the overhead of a full-time hire. We show up in your tools, your standups, and your Slack.
An advisory engagement built around a diagnosis. We audit what's happening, hand you a clear plan with priorities attached, and execute alongside your team as much or as little as you need.
Scoped, project-based work with a clear deliverable and a deadline. You know what you're getting and when. Good for a single build, a platform migration, or a specific fix that needs to happen and stay fixed.
Not sure which one fits? Tell us the problem, we'll tell you the engagement.
What each engagement includes.
Ordered from the most involved to the least. Most engagements are a mix, this is the general shape of each.
| Fractional CPO |
Fractional Employee |
Consultant | Contractor | |
|---|---|---|---|---|
| Sets strategy & roadmap priorities | ✓ | ✕ | ✓ | ✕ |
| Executes hands-on work | ✓ | ✓ | ✓ | ✓ |
| Embedded daily in your tools & standups | ✓ | ✓ | ✕ | ✕ |
| Ongoing, recurring engagement | ✓ | ✓ | ✓ | ✕ |
| Accountable for team output & delivery | ✓ | ✕ | ✕ | ✕ |
| Can coordinate a dedicated India build team | ✓ | ✓ | ✓ | ✕ |
| Fixed scope with a defined deadline | ✕ | ✕ | ✕ | ✓ |
| Best for a single, well-defined project | ✕ | ✕ | ✕ | ✓ |
How we price.
Every engagement is billed hourly. The more embedded the role, the more we ask for a minimum hour commitment, so we can actually move the needle instead of context-switching between five different clients.
Not sure which function you need?
That's normal. Most of the problems we get called in for touch product, data, and operations at once.
Selected work.
A sample of the kind of problems we get called in for. Most of our work happens under NDA, so names and numbers below are illustrative. Specific client references are available on request.
Fixing broken ad tracking that was quietly killing performance
A brand's Meta ad performance had been declining for months. Campaigns were being paused and reworked based on numbers nobody could fully explain, but the creative was never the real problem.
Audited the full tracking chain from ad to landing page and found a batch of broken links pointing to outdated URLs, silently dropping a meaningful share of paid traffic before it ever reached the site.
Fixed the links and rebuilt the tracking. Reported performance jumped, not because the ads got better, but because they were finally being measured correctly.
Tracking down blank screens and failed payments before they cost more customers
Customers were intermittently hitting blank screens at checkout, and a share of payments were silently failing, with no clear pattern and no one owning the issue.
Reproduced the failures across browsers and devices, traced them to a conflict between a third-party script and the checkout flow, and worked with the dev team to isolate and fix it.
Blank screens and failed payments stopped, and a monitoring check went in place so the same failure mode gets caught automatically next time.
Using product-level data to decide what belongs on the PDP and PLP
A brand's product and listing pages were arranged by guesswork. Older products got the same real estate as the strongest sellers, and conversion was suffering for it.
Analyzed product-level performance data to identify the actual top performers, then rebuilt the PDP and PLP layouts to surface those products first.
Conversion improved on the pages that mattered most, and the brand had a repeatable, data-backed process for deciding what to feature next.
Unifying Amazon, GA4, Meta, Klaviyo, and Shopify into one dashboard
A brand's data was scattered across five different platforms: Amazon, Google Analytics, Meta, Klaviyo, and Shopify. Nobody had one place to see how the business was actually performing.
Built a single dashboard that pulled and reconciled data across every channel, so metrics could be compared and cross-referenced instead of living in five separate tabs.
Leadership got one source of truth for the business, and could finally see how channels influenced each other instead of looking at each in isolation.
Rebuilding a storefront's ad tracking from scratch
A DTC apparel brand's Meta and Google ad accounts were reporting numbers that didn't match Shopify. Nobody could tell which campaigns actually worked.
Audited the pixel and GA4 setup, rebuilt server-side tracking, and stood up a dashboard tying ad spend to actual revenue.
Leadership could finally see true ROAS by campaign, and cut spend on channels that were quietly losing money.
Standing up QA and support for a fast-growing marketplace
A marketplace seller platform was shipping features faster than it could test them, and customer issues were piling up in a shared inbox.
Built a QA process for releases, set up Jira workflows the team actually used, and triaged the customer issue backlog.
Release-related complaints dropped, and the team had a clear system for catching bugs before launch instead of after.
Turning three spreadsheets into one dashboard
A B2B SaaS company's leadership team was pulling numbers from three different tools before every board meeting.
Consolidated data sources, configured a single reporting pipeline, and built a live dashboard around the KPIs that actually mattered.
Board prep dropped from days to an afternoon, and the numbers finally agreed with each other.
Fractional product leadership for a seed-stage app
A seed-stage consumer app had engineers but no one setting priorities, and the roadmap changed every week.
Stepped in as fractional CPO, ran discovery with users, and built a prioritized roadmap the team could actually execute.
The team shipped its first stable release cadence and could tell investors what was coming next with confidence.
Sound like a problem you have?
Tell us what's going on and we'll tell you honestly whether we can help.
The IEEPA refund window is closing
The CAPE portal opened April 20. Phase 1 covers less than most DTC brands realize, the protest clock is running on your oldest entries, and some windows may already be closing.
On February 20, 2026, the United States Supreme Court ruled 6-3 in Learning Resources, Inc. v. Trump that the International Emergency Economic Powers Act does not give the President authority to impose tariffs. The decision invalidated the IEEPA-based reciprocal tariffs applied from April 2025 onward, along with the so-called fentanyl tariffs on goods from China, Canada, and Mexico.
The practical result: approximately 330,000 businesses paid or deposited an estimated $166 billion in duties across more than 53 million import entries between roughly March 2025 and February 24, 2026. Those duties were illegally collected. The Court of International Trade ordered U.S. Customs and Border Protection to refund them. CBP built a new system to do it.
That system, called CAPE (Consolidated Administration and Processing of Entries), went live in the ACE portal on April 20, 2026. As of April 26, importers and brokers had submitted approximately 75,300 CAPE declarations covering more than 11.2 million entries. That leaves around 42 million entries still unfiled against, and the deadlines on some of those entries are not months away.
What was struck down, and what wasn't The ruling struck down IEEPA tariffs only. Section 301 duties, Section 232 duties, and standard processing fees remain in full effect and are not refundable. The IEEPA-attributable portion of each entry is the only part that's refundable. Brands submitting refund requests that include Section 301 or 232 amounts in the IEEPA-attributable figure get rejected by ACE at the entry level, which adds weeks of cycle time.
The three paths to a refund Path 1: CAPE Phase 1 covers unliquidated entries and entries liquidated within 80 days of your CAPE submission, currently reaching back to approximately February 1, 2026. CBP estimates Phase 1 covers roughly 63% of total IEEPA tariffs paid. Refunds, including statutory interest, arrive via ACH in an estimated 60 to 90 days from accepted declaration.
Path 2: CBP Protest under 19 U.S.C. Section 1514, for entries liquidated and outside the 80-day CAPE window but still within 180 days of liquidation. This is the critical path for 2025 entries that have already liquidated, since CBP has been liquidating many faster than the standard 314-day cycle. Steptoe's trade team specifically flagged that importers with 2025 liquidations should file protests in a timely manner, since some protest windows on April, May, or June 2025 entries may be closing this month.
Path 3: Court of International Trade action, for entries where the 180-day protest window has passed. This carries a two-year statute of limitations but generally does not award interest, unlike the first two paths.
How to run your entry audit Pull your ES-003 (importer activity) and ES-701 (liquidation notice) reports from ACE, filtering for Chapter 99 HTS codes beginning with 9903.01 and 9903.02. Sort entries into the three buckets above by liquidation date, separate the IEEPA-attributable duty from Section 301/232 amounts, and total each bucket. If you've never accessed ACE and don't have a broker relationship, that's the signal that filing directly is not viable for your business.
For refund exposure under $25,000, self-filing is reasonable. Between $25,000 and $150,000, a customs consultant catches common rejection patterns. Above $150,000, use a licensed customs broker.
The dual-track approach, filing a CAPE Declaration where eligible and a protest as backup where liquidation status is ambiguous, is specifically recommended by trade counsel including Sandler Travis and Steptoe.
The accounting reality IEEPA tariffs paid in 2025 were deductible as cost of goods in that year. The refund is taxable income in the year received, creating a mismatch your CFO needs to plan for. Brands that publicly communicated tariff-driven price increases should review those communications with counsel before posting about refund recovery, given emerging consumer class action exposure.
What comes next Section 122's 10% global surcharge, which replaced the voided IEEPA framework, expires July 24, 2026 unless extended. USTR opened two sweeping Section 301 investigations in March 2026 designed to build a permanent, statutorily anchored replacement, with historical timelines running 6 to 18 months to implementation. The overall direction of U.S. trade policy is toward more tariffs with a more durable legal structure, not fewer tariffs.
At $166 billion across 330,000 importers, average duty exposure is just over $500,000 per business. For a $5M DTC brand that imported consistently from China in 2025, IEEPA duties likely represent $400,000 to $800,000 in refundable duties plus interest. The protest deadline on your April 2025 entries may be this month.
Sources
U.S. Supreme Court, Learning Resources, Inc. v. Trump, February 20, 2026; CBP IEEPA Duty Refunds official page, May 6, 2026; White and Williams, April 2026; Holland and Knight, April 2026; Baker Tilly, May 2026; Steptoe, April 2026; Morgan Lewis, March 13, 2026; Duane Morris, April 2, 2026.
Have a problem like this one?
Tell us what's going on. We'll tell you honestly whether we're the right fit.
Start a projectTell us what's broken.
Fill this out and we'll get back to you within one to two business days.
What happens next
We read what you send and ask clarifying questions if we need to.
We get on a short call to understand the problem, not just the request.
We tell you honestly whether we're a fit, and propose an engagement.
Prefer email?
theecommerceoperator@gmail.com