The hour your PPC dashboard eats is the hour you’ll never get back
Cross-border operators don’t have a time-management problem. We have a time-leakage problem, and it’s structural. The Shenzhen supplier replies at 3 a.m. your time. Amazon Seller Central’s reporting refresh lands mid-morning. TikTok Shop’s flash sale window overlaps with your kid’s bedtime. By the time you’ve triaged the inbox, reconciled the ad spend, and answered the freight forwarder, the one block of deep work you actually reserved — the one that would have moved margin instead of just maintaining it — has evaporated. A to-do list will never show you where that hour went. A shape might. That’s the interesting premise behind Reassign, a solo-built scheduling tool from Leo Spanovic that just went live on Product Hunt, and it’s worth ten minutes of your attention even if you never install it.
What Reassign actually is, and why the framing matters more than the features
Strip away the launch-day polish and Reassign is a 24-hour radial dial. Midnight sits at the top, noon at the bottom, and your day is drawn as a circle rather than a vertical column. You drag blocks around that dial to reshape the day; color encodes the “area of life” and fill pattern encodes how a block feels — flow, grind, recharge, or drain, per the maker’s own description. It installs as a PWA, ships with a Chrome extension, and syncs two-way with Google Calendar, Outlook, Todoist, and Linear. There’s a public REST API at reassign.dev, an iPhone companion and a Raycast extension queued next, and — the part that actually caught my eye — an MCP server so you can ask Claude or ChatGPT to “find 45 minutes for a run” and have the block land on the dial live. Every AI-generated change comes with a 30-minute undo. Pro is free for seven days, no card required.
Here’s why I care, and it isn’t the radial layout. It’s the diagnosis underneath it. Spanovic writes that he spent ten years drawing his tomorrow as a circle on paper, and that the problem a to-do list never surfaced was this: the hour he wanted for building was always the first thing his day ate. That is not a productivity aphorism. That is a precise description of what happens to a cross-border seller’s sourcing window, creative-testing window, or supplier-negotiation window the moment a marketplace throws an exception at you. The urgent always cannibalizes the compounding. If you’ve ever closed a Q4 with great revenue and terrible margin because you never once sat down to renegotiate freight rates, you already understand the failure mode.
Why Amazon sellers should care more than Shopify ones
DTC operators on Shopify have a certain amount of structural slack. Your store doesn’t suspend you for a late shipment, and your ad account doesn’t get a policy strike because a listing image changed. Amazon sellers live under an operational clock that punishes calendar neglect directly: account health metrics, buy-box suppression, inventory performance index thresholds, and A-to-Z claims all have response windows measured in hours, not days. Add TikTok Shop flash-sale scheduling and Temu or SHEIN restock cadences on top, and the number of hard-edged deadlines in a week starts to look less like a calendar and more like a minefield.
A radial view has one genuine advantage over a list here: it makes density visible. Twenty-four hours drawn as a ring shows you, at a glance, that you’ve stacked four supplier calls into a three-hour window on the same morning your ad reports refresh. A vertical list of the same events looks fine. The ring doesn’t lie. Whether that visual honesty changes your behavior is a separate question, and I’ll get to my skepticism below.
The MCP angle is the real story, and it cuts both ways
The reason Reassign is more interesting than the fiftieth calendar app on Product Hunt is the Model Context Protocol integration. MCP is quietly becoming the connective tissue between AI assistants and the tools operators already run — and if you’re building a cross-border stack in 2025, you should be paying attention to which of your vendors expose an MCP server, because that determines whether your AI assistant can act on your data or merely talk about it.
Concretely: imagine an MCP-connected assistant that reads your Helium 10 keyword data, your Klaviyo flow performance, and your calendar, then proposes a reshuffled week based on which SKUs need creative refreshes before a Prime Day deadline. That’s the direction. Reassign is a small, early proof that the plumbing works — you ask in natural language, a block appears on a dial, and you get a 30-minute undo because, as Spanovic puts it, he doesn’t trust AI blindly either. That last detail is the most operator-minded thing in the entire launch. Anyone who has watched an AI tool silently rewrite a campaign structure or a pricing rule knows exactly why a bounded undo window matters more than the feature itself.
Where the math breaks
Now the pushback. A radial dial is a beautiful diagnostic and a mediocre system of record. The moment your week involves three time zones, a factory that runs on China Standard Time, and a marketplace whose reporting day boundary doesn’t match yours, a 24-hour circle stops being a clean abstraction and starts being a lie — because your “day” isn’t 24 hours of local time, it’s a rolling window that spans two calendars. Reassign’s two-way sync with Google Calendar and Outlook helps, but sync is not the same as timezone-native planning, and the source doesn’t claim otherwise.
There’s also a harder commercial question. Reassign is a solo project with no team and no disclosed budget, built by someone holding a full-time remote job with three kids. That’s admirable and it’s also a concentration risk. If you’re going to route your operating rhythm — even partially — through a tool, you should ask what happens to your data and your integrations if the maker’s side project loses a funding round it never had. The public REST API and the MCP server are good hedges here, because they mean the underlying data isn’t hostage to the UI. But “not disclosed” is the honest answer to almost every durability question you’d want to ask about a launch-stage tool, and you should price that risk accordingly.
What cross-border operators can actually borrow from this
I don’t think most sellers should adopt Reassign tomorrow. I do think the thinking behind it is worth stealing, and there are four transfers that hold up.
First, protect the compounding hour by shape, not by intention. Spanovic’s paper-circle habit existed because a list let him lie to himself. For a seller, the compounding hour is usually one of three things: supplier relationship work, creative and listing iteration, or unit-economics review. None of those are urgent. All of them are the reason you’ll still have a business in eighteen months. Draw your week as a ring, find the hour, and treat its shape as a commitment.
Second, treat AI actions as reversible by default. The 30-minute undo is a design principle you can port to your own automation stack. Any AI agent touching your Amazon Ads bids, your email flows, or your repricing rules should write to a staging layer with a rollback window. If your current tooling can’t undo an AI change in under an hour, you don’t have an AI workflow — you have an AI liability.
Third, watch MCP adoption as a vendor-selection criterion. When you’re evaluating a new SaaS — a ShipBob for fulfillment, a Gorgias for support, a Loop for returns — ask whether they expose an MCP server or a well-documented API. The tools that do will compound; the ones that don’t will become manual tax.
Fourth, separate diagnostic tools from systems of record. Use Reassign (or a whiteboard, or a spreadsheet) to see your week. Keep your actual commitments in the system your team already trusts. Don’t let a beautiful interface become a second source of truth.
The uncomfortable question the launch asks
Spanovic closes his post with a question: do you see your day as a list, or as a shape? For cross-border operators, the honest answer is usually “as a list I never finish.” That’s worth sitting with. The reason Q4 destroys so many sellers isn’t demand — it’s that the operating rhythm was never designed for the load, and no amount of hustle patches a structural problem. A radial dial won’t fix your supply chain. But the discipline of asking where the hour went is the difference between a seller who scales and a seller who just gets busier.
What I’d watch / test next
This week, do three things. First, spend twenty minutes drawing your last seven days as a ring — not what you planned, what actually happened — and mark which blocks were flow, grind, recharge, or drain. You’ll find your leakage in about four minutes. Second, if you run any AI automation against ad spend, pricing, or email, audit whether it has a rollback window; if it doesn’t, build one before you scale it. Third, shortlist two vendors in your stack and check whether they publish an MCP server or a serious API — that’s your 2026 integration roadmap forming in real time. As for Reassign itself: the seven-day Pro trial needs no card, so the cost of testing the MCP handoff is an afternoon. Watch whether the timezone handling survives contact with a real cross-border week, and watch whether the solo-maker risk gets addressed with a public roadmap or a data-export guarantee. If it does, it graduates from interesting experiment to something I’d actually recommend. If it doesn’t, steal the circle and keep your calendar.
