CompassPad — Find what was just built.

Figma is a design tool that runs in the browser and lets several people edit the same file at once. Cursors are visible, changes appear live, and a comment can be attached to a specific element, which removes the file-versioning and hand-off problems that a desktop design tool creates. The product covers interface design: frames and layout, components with variants, a shared library of styles and components across files, and prototyping with transitions between screens. Design tokens and variables let a theme be changed in one place, and the developer hand-off view exposes measurements and assets. Because the file lives in the browser, the same link serves designers, engineers, and stakeholders, which is why the tool spread beyond design teams. The tradeoff is dependence on a hosted service: there is no offline-first mode comparable to a desktop application, and the organisation's design assets live in a vendor's account.

Stripe is a payments platform that handles card and alternative payment methods, subscriptions, invoicing, and the money movement around them. A developer integrates through an API and hosted or embedded components, and the platform absorbs the network of acquiring banks, card networks, and local payment methods behind that interface. The breadth is the reason it is the default choice for online businesses. Beyond accepting a payment, the platform covers subscription billing with proration and trials, usage-based metering, invoicing, tax calculation, fraud screening, and payouts to connected accounts. Each of those is a product in its own right that a team would otherwise build or buy separately. The tradeoff is cost and control. Pricing is per transaction and adds up at scale, which is why larger businesses negotiate rates or move some volume to a direct acquirer. The platform is also opinionated about the merchant of record and the payout model, so businesses with unusual money-flow requirements sometimes find the constraints binding.

Notion is a workspace where documents and databases are the same primitive. A page contains blocks, and a database is a collection of pages with typed properties, which means a task list, a content calendar, and a project tracker are all views over pages rather than separate applications. The product grew by replacing several tools at once: notes, a lightweight wiki, a task board, and a simple database. Because everything shares one editor and one permission model, a team can link a project page to a task database and see the same records from both. Templates and a public gallery spread reusable structures. The tradeoff is depth. A Notion database is not a relational database, so reporting is limited compared with a real BI tool, and large datasets slow down. Teams that push it into that role tend to add a proper database and analytics stack alongside it.

Cursor is a code editor that embeds AI assistance directly into the editing surface. It is built as a fork of VS Code, so extensions, themes, and keybindings carry over, but the assistant is a first-class part of the interface rather than a plugin. The core interaction is the inline edit: select code, describe the change in natural language, and review a diff before accepting. Alongside that, a chat panel can read the open files and answer questions about the codebase, and an agent mode can make multi-file changes with a plan the developer approves. The editor indexes the repository so answers reference the project's own code rather than generic patterns. Teams that adopt it typically keep a review step, because the assistant's output still needs the same scrutiny as any other contribution. The company publishes a changelog and documentation, which is what makes the feature set checkable.

Shopify is a hosted ecommerce platform. A merchant gets a storefront, a checkout, payment processing, inventory, and order management without operating any of it, and the platform handles the security and compliance work that accepting card payments requires. The product's scale comes from its app ecosystem. Anything the platform does not do natively — a loyalty programme, a subscription option, a review system, a warehouse integration — is available as an app, which means the platform can be extended without the merchant writing code. Themes control the storefront, and a headless mode exposes the commerce APIs for a custom frontend. The tradeoff is cost at scale and the constraint of a hosted model. Transaction fees apply when a third-party payment provider is used, app subscriptions add up, and the checkout cannot be fully customised outside the platform's extension points. Merchants with unusual requirements sometimes move to a headless platform to get that control back.