Mike Oustamanolakis, PhD
← Work

A document compiled per buyer

No two people keep time the same way, which makes a shelf of fixed planners a shelf of near-misses. There is no product here to choose from. There is a compiler.

Problem
A planner that fits nobody exactly is bought once and abandoned
Scale
372 templates · 52 devices measured · 27 languages
Role
Architect, builder and product owner
Status
Built · sandbox orders verified end to end · not yet selling
The organize.ink homepage: the headline ‘No two people should have the same planner’, a sample weekly spread on a reMarkable tablet, and a bar of counted figures.
The refusal is the pitch: no two people should have the same planner, so we do not sell one.

Status. The builder, the template library and the render pipeline are complete, and the full order path has been verified end to end in Stripe sandbox. It is not yet selling — the remaining step is the live key.

The problem

An e-ink planner has to fit a specific screen at a specific resolution, start on the date the buyer actually starts, run in the buyer’s language, and carry the public holidays of the place the buyer lives. Every fixed product compromises on at least two of those, and the compromises are invisible until the file is on the device and wrong.

The regional layer is where most products give up entirely. A national holiday list is not what a person in Scotland or Bavaria needs, and bolting one on the back of the document is a gesture rather than a feature.

What I built

A configurator and a rendering pipeline. The buyer states their device, dates, language and jurisdiction; the system compiles a document that exists only for them, and ships it with its own code because no two are alike. 52 tablets have been measured to the millimetre so that a page fits its screen rather than approximately fits a category of screens.

Holidays come from the same corpus that powers timesys.pro, so Scotland gets 2 January and St Andrew’s Day and no Easter Monday, and Bavaria gets Epiphany — carrying the source and the confidence with them.

The organize.ink builder: the configurator where a buyer selects device, dates, language and jurisdiction.
The builder is the product. Everything downstream is compilation.

The decision that shaped it

Selling a configured artefact rather than a catalogue item removed the cart, the variants and the stock model in one move — and makes hosted Stripe Checkout the correct payment path, which puts the merchant of record and the VAT obligation where they belong rather than on a one-person company.

The same provenance rule as everything else: where a future date is projected rather than gazetted, the planner says so instead of guessing quietly. A planner that silently invents a bank holiday is worse than one that admits it does not know.

The organize.ink pricing page, showing what a generated planner costs.
One corpus of templates, priced per compiled document rather than per SKU.

What it demonstrates

Building the same corpus-to-many-deliveries model as timesys, aimed at consumers instead of treasury teams: high fixed cost to build the library, near-zero marginal cost per buyer, and no two outputs identical.

Visit organize.ink →