Skip to content
Guilherme MartinsPT Português, ler em português
All cases

Independent product

Priorize.me

A collaborative prioritization app built on the Eisenhower matrix, with shared boards that update in real time. In public beta.

Role
Creator and developer
Period
Sep 2026 - present
Stack
React 19, TypeScript, TanStack Router, TanStack Query, Supabase (Postgres, Auth, Realtime), Playwright
The Priorize.me landing page, in Portuguese: the headline “Stop treating everything as urgent” beside an example board with the four quadrants.

The problem

Teams treat too many requests as urgent, and the real priorities live in people's heads or in scattered lists. Priorize.me makes the decision explicit: you capture a request in a Backlog, judge its urgency and importance, and choose Do, Schedule, Delegate or Eliminate, on a board everyone involved can see.

Approach

Boards are private and shared by invitation or join link, with owner, editor and reader roles. Changes reach everyone on the board in real time, and sign-in uses a link sent by email instead of a password.

An MCP server lets compatible AI clients list, create and move tasks with the account's own permissions. The interface ships in Portuguese and English.

Key decisions and trade-offs

The board is the unit of tenancy and the database is the authority. Row-level security guards the public tables, writes to tasks and members go through database functions that check the caller's role, and hiding a button in the interface never counts as authorization.

Realtime carries changes but is not state. The database stays the source of truth, each task has a version, and the client applies one rule wherever state converges: the higher version wins. The server computes positions under a per-board lock, so concurrent moves cannot interleave.

The product stays on Supabase without an abstraction layer, but the dependency is confined to boundaries that CI checks, with an inventory of what replacing each service would cost (low for the database, high for row-level security and auth).

The MCP server follows the app's domain: a change to data or a function a tool uses must update that tool and its integration test in the same pull request.

Validation

Each test declares its layer in the file name: unit and component tests in Vitest, database tests in pgTAP with race-condition sensors, integration tests for the MCP server, and Playwright end-to-end suites ranked by severity. The critical journey (sign in, create a board, move a task) gates product pull requests, and the public pages run axe checks.

Status

Priorize.me is in public beta: free, with sign-up required and no card. The code repository is private.

Facts checked on October 11, 2026.