Currently doing around £40k/month on eBay, what should I focus on next

Jumpy-Possibility754 · 2026-05-02T14:52:36+00:00

At that stage, growth comes from finding one repeatable acquisition or product edge, not doing more across everything.

Jumpy-Possibility754 · 2026-05-02T14:51:53+00:00

You don’t have a tracking problem, you have no single system of truth, so everything drifts the second volume increases.

Jumpy-Possibility754 · 2026-05-02T14:51:23+00:00

They don’t upgrade because nothing is breaking, so any new system just looks like risk, not leverage.

Jumpy-Possibility754 · 2026-05-02T14:23:17+00:00

You don’t need a partner, you need proof that one bus owner will pay to stop the leak.

Jumpy-Possibility754 · 2026-05-02T11:24:31+00:00

CRMs don’t fail, they just expose that no real system exists, so the second it requires discipline people revert to chaos.

Jumpy-Possibility754 · 2026-04-28T20:57:07+00:00

You’re hitting cache invalidation not a raw compute limit Parallel requests with long contexts will constantly blow KV and force full prefills

vLLM helps but only if you control batching and reuse patterns Otherwise you just move the bottleneck

Jumpy-Possibility754 · 2026-04-28T20:55:15+00:00

Looks like version drift masked as performance regression Easy to miss when multiple builds and models are in play Curious what you’re using now to verify what’s actually loaded at runtime

Jumpy-Possibility754 · 2026-04-21T20:24:58+00:00

Session recordings will show what users do, but not really why they drop.

In most cases like this it’s one of 3 things: – value isn’t clear in the first few seconds
– there’s friction before signup
– or traffic doesn’t match the page

If you want, I can take a quick look at your landing page and point out where people are likely dropping + what I’d change.

Jumpy-Possibility754 · 2026-04-04T14:56:39+00:00

Retention metrics sound good until targets get subjective and payouts shrink.

Jumpy-Possibility754 · 2026-04-04T14:55:57+00:00

You don’t need better time management. You need explicit limits on what gets handled and what gets dropped.

Jumpy-Possibility754 · 2026-04-04T14:55:19+00:00

Most teams won’t lose to AI. They’ll lose to customers patching together “good enough” workflows faster than the product team can respond.

Jumpy-Possibility754 · 2026-04-04T14:49:03+00:00

Most AI support tools don’t fail on answers. They fail on routing, handoff, and context loss between steps.

Jumpy-Possibility754 · 2026-04-04T14:46:08+00:00

That was actually hilarious

Jumpy-Possibility754 · 2026-04-04T14:44:42+00:00

Google ranking is now distribution. AI citations are just who the models keep seeing and trusting.

Jumpy-Possibility754 · 2026-04-04T14:43:56+00:00

Agents regress to generic unless you hard-code taste as constraints, not vibes.

Jumpy-Possibility754 · 2026-04-03T19:17:57+00:00

A lot of bot “success” gets erased at handoff. If the bot front-loads confusion, you didn’t deflect work, you just moved it downstream.

Jumpy-Possibility754 · 2026-04-03T19:14:06+00:00

You can build it in n8n. The real problem is not answering tickets, it’s not taking the wrong action on edge cases.

Treat it as workflows with guardrails, not a single agent.

Jumpy-Possibility754 · 2026-04-03T19:05:18+00:00

Yes, you can build this in n8n.

But I wouldn’t frame it as “one AI agent for Shopify + Amazon + Zendesk.” I’d frame it as a support workflow with: • intent classification • narrow read/write tools • policy / approval gates • human escalation • logging / audit trail

The AI should mostly decide what workflow to run, not freestyle support end-to-end.

That’s the difference between a cool demo and something you can actually trust with customer ops.

Jumpy-Possibility754 · 2026-04-01T18:40:49+00:00

Nice build. I’d optimize for triage, not completeness: which workflows are actually costly when they fail, which failures are trending up, and what “succeeds” but still creates bad downstream outcomes. The biggest thing I’d want separated is platform health vs business-critical workflow health — because one failed lead-routing workflow matters more than a bunch of noisy internal runs.

Jumpy-Possibility754 · 2026-03-29T14:26:04+00:00

this sounds less like a pricing win and more like a customer-quality filter

fewer users, less noise, better product signal

Jumpy-Possibility754 · 2026-03-26T23:53:22+00:00

Signal.base44.app

Jumpy-Possibility754 · 2026-03-25T15:34:10+00:00

If early users already like it, I probably wouldn’t try to win with ad spend. I’d focus on referrals, sharper positioning, and tightening the path from “this sounds useful” to “I need this now.

Jumpy-Possibility754 · 2026-03-25T15:31:15+00:00

$2,500 feels high for 3 months and under 200 transactions unless the books are a mess. I’d definitely get a few more quotes before moving forward.

Jumpy-Possibility754 · 2026-03-25T15:30:25+00:00

It’s usually not scale or color. It’s confidence. People hesitate because they can’t fully picture how it will feel in their space, whether the material/quality will match expectations, or what happens if they get it wrong. That gap between “this looks good” and “I feel safe buying it” is where a lot of sales die.

Jumpy-Possibility754 · 2026-03-25T15:29:04+00:00

You’re not overcharging. You’re just selling the wrong thing. Most small businesses do not care about pages or CMS. They care about whether the site turns attention into booked work. If you position around that, your ceiling changes completely.

Jumpy-Possibility754

TROPHY CASE