The canvas tool that won’t help you run a supply chain — and why that’s exactly the point
Most software I review for this audience promises to compress a workflow: fewer clicks to reprice a SKU, fewer hours to reconcile a 3PL invoice, fewer spreadsheets between a supplier quote and a landed-cost model. Expand Board for macOS promises the opposite. It gives you an infinite surface, no templates, no enforced structure, and a maker who explicitly says there are “no limits or instructions.” On paper that is the worst possible pitch to an operator whose entire job is constraints. In practice, it is the first tool I have seen in months that treats the messy, pre-decision phase of cross-border work as a first-class problem rather than a form to fill in. That phase — supplier shortlists, tariff scenarios, creative angles, TikTok hook variants, Q4 inventory bets — is where most sellers actually lose money, and it is the phase that Notion databases, Asana boards, and Amazon Seller Central reports are all structurally bad at holding.
What Expand Board actually is, and who it’s for
The maker, Gabriel, launched the product under the handle sgroiga and describes it as a board where “you can use as many elements and text pieces as you like,” built because he wanted something “better than an iPad or notepad” for collecting thoughts in a structured way. The framing is deliberately anti-project-management: “It’s just you and the board.”
Two technical facts matter more than the marketing copy. First, it is a native macOS application, not a web app — the maker confirmed this directly when asked about data ownership. Second, there is no cloud backend; the only sync option is iCloud, which the maker noted as an optional layer rather than the default. That combination — local-first, desktop-native, no account wall — puts it in a very different category from the browser-canvas tools most teams default to.
The comment thread is unusually informative for a Product Hunt page. Viktor LOOSZ said he would try it specifically because Miro is being acquired, which is the kind of switching trigger that actually moves users. Oren Reuveni argued that “native macOS thinking tools still feel better than most web canvases” and called limitless boards for expanding ideas “a clean, useful wedge.” Gal Dayan — himself a maker of a competing product, Dial — praised the double-click-to-add interaction and breadcrumb navigation as a fix for “the usual infinite-canvas problem of losing where you are,” then asked whether search works across nested boards. The maker confirmed search is global, and Dayan pushed back that a per-board toggle would just add friction. That exchange is worth reading in full because it is the clearest articulation of the product’s actual design bet.
The nested-board question nobody answered cleanly
Muhammad Ahmed asked whether nested boards hit a complexity ceiling where “keeping context becomes difficult.” The maker’s answer was that there are “no technical limitations, no matter how many boards we need to test or their height and width,” though he conceded it “may look bad when printing documents at some point.” Translation for an operator: the tool will not stop you from building a 40-board monster, and it will not save you from it either. That is a real answer, and an honest one, but it is not a solution.
The problem it solves that your stack doesn’t
Here is the cross-border scenario I keep running into. A seller is evaluating a new category — say, collapsible pet crates for the EU market. The work involved is not a task list. It is a pile of half-formed things: three supplier quotes in different currencies, a freight forwarder’s email about dimensional weight, a competitor’s Amazon listing that seems to be ranking on a keyword you hadn’t considered, a note that the SHEIN version of the product is priced 40% below your landed cost, a screenshot of a TikTok Shop video doing 2M views with a hook you could adapt, and a vague instinct that the whole thing is a trap.
Where does that pile live today? Usually in a Notion page that becomes unreadable at around item 30, or a Miro board that three people edit until nobody trusts it, or — most commonly — a folder of screenshots and a Slack channel. The reason it never gets structured is that structuring it prematurely kills the thinking. You do not yet know which of those five data points is the load-bearing one. A database forces you to pick columns before you know what matters.
Expand Board’s bet is that the right primitive for this phase is spatial, not relational. You drop elements anywhere, move them as relationships become clear, and the layout itself becomes the argument. That is not a new idea — it is essentially the Apple Freeform premise, and it is the premise behind Miro, FigJam, and Milanote. What is different here is the refusal to add collaboration, permissions, templates, or a web client. The product is betting that the friction those features introduce is worse than the isolation they relieve.
Why Amazon sellers should care more than Shopify ones
A Shopify DTC operator already has a natural home for loose thinking: the brand’s own Notion or Linear workspace, plus a creative team that expects briefs. The canvas is a nice-to-have.
An Amazon seller does not. Their operating reality is Seller Central, Helium 10, and a spreadsheet. When they want to think about a new ASIN, a bundle strategy, or whether to fight a hijacker, there is no surface designed for it. They open a Google Doc and it dies. A local-first canvas that requires no login, no per-seat pricing, and no IT approval is genuinely lower-friction for that person than anything in the SaaS category. The same logic applies to Etsy sellers managing seasonal collections and eBay sellers juggling liquidation lots — solo operators with no collaboration requirement and a strong preference for tools that do not phone home.
What cross-border operators should borrow from this
Three transferable ideas, independent of whether you install the app.
Local-first as a procurement criterion. The Curious Kitty question in the thread — about data ownership, export, backup, and future-proofing — is the single most important question any seller should ask before adopting a tool, and almost nobody asks it. If your supplier negotiation notes, your margin models, and your ad account structures live in a cloud tool that gets acquired, pivots, or raises prices, you have outsourced the continuity of your business to someone else’s runway. The maker’s answer here — macOS app, no cloud, optional iCloud sync — is a legitimate differentiator, and it is the reason Viktor LOOSZ’s Miro comment landed. When Miro changes hands, users with ten years of boards have to think about migration. Users of a local file do not.
Global search as a default, not a setting. The Dayan exchange is a small masterclass in product judgment. Dayan suggested a per-board search toggle; the maker agreed it was a good idea; Dayan then reversed himself, arguing that “global search is honestly the better default anyway — a per-board toggle would just be extra friction for the common case.” That is the correct call, and it maps directly onto how operators work. When you are hunting for the freight quote you remember seeing somewhere, you do not know which board it is on. Scoped search is a feature for people who already have good information architecture. Most sellers do not.
Breadcrumbs over dashboards. Dayan’s praise for breadcrumb navigation as the antidote to “losing where you are” on an infinite canvas is worth stealing for your own internal docs. The failure mode of every sprawling workspace — Notion, Confluence, Coda — is that depth becomes indistinguishable from chaos. Any structure that shows you the path back to the root is worth more than a prettier overview page.
Where the math breaks
The pricing is not disclosed anywhere in the source material, which is itself a signal. For a solo operator, a one-time macOS purchase is easy math. For a team of five account managers at an agency, an app with no cloud sync and no collaboration is a non-starter regardless of price — you cannot share a board, so you cannot share the thinking, so the tool stays personal and the team stays on Miro. That is a deliberate tradeoff, not an oversight, but it caps the addressable market hard.
Where my judgment says it falls short
I like the wedge. I am not convinced the product survives contact with a real operator’s year.
The printing concession is a tell. When the maker says nested boards “may look bad when printing documents at some point,” he is describing the moment the canvas has to become an artifact. Cross-border work constantly has to become an artifact — a supplier brief, a landed-cost sheet, a creative brief for a TikTok Shop agency, a Q4 buy plan for a lender. A tool that is excellent at thinking and awkward at exporting will get abandoned at exactly the handoff point where its value should compound. There is no mention of PDF export quality, structured export, or API access in the thread. Until that is solved, Expand Board is a pre-decision tool, not a decision tool.
No cloud means no phone. A meaningful share of supplier and factory communication happens on mobile, in WhatsApp and WeChat, often from a trade show floor or a factory visit. A macOS-only canvas is invisible in that context. iCloud sync does not fix it — there is no iOS client mentioned. For an operator doing sourcing trips, that is a real gap.
The AI question went unanswered. rick segal made a pointed comment about “the stupidity of the ‘AI’ within product hunt” while praising the app, and the AI framing shows up in the commenter badges on the page. But nothing in the thread describes any AI capability in the product itself. I would treat any implication of AI features as unverified. That is fine — the product does not need AI — but sellers who have been trained to expect it should not assume it.
The switching trigger is real but shallow. LOOSZ’s Miro comment is the strongest demand signal on the page, and it is a one-time event. Tools that win on a competitor’s acquisition news tend to lose the next cohort of users to whatever the next acquisition triggers. Expand Board needs a reason to be chosen on a Tuesday in March, not just in the week Miro’s deal closes.
What I’d watch / test next
This week, if you are evaluating whether a canvas belongs in your stack, do three things. First, take one live sourcing or launch decision you are currently muddling through and dump every artifact into a single board — quotes, screenshots, listing links, freight emails — without organizing it. If the spatial layout surfaces a relationship you had not seen, the category is worth your time; if it just looks like a mess, your problem was never the tool. Second, audit your current workspace against the Curious Kitty test: can you export everything you own in a format you control, and what happens to your data if the vendor is acquired? Most sellers will fail this and should fix it regardless of Expand Board. Third, watch whether the product ships mobile, export, or any real collaboration primitive in the next two quarters. If it stays deliberately local and solo, it is a personal thinking tool for owner-operators and should be budgeted as such — not as a replacement for Miro, Notion, or whatever your team actually coordinates in. The honest read: a well-made, opinionated, narrow tool that solves a real problem for a specific kind of seller, and one I would rather see exist than another AI wrapper promising to run your ads.
