PRJ-10SYSTEM CASEPRE-RELEASE · ACTIVELY DEVELOPEDPRODUCT · WINDOWS PRODUCTIVITY

Rail

EDGE-FIRST FAST-CAPTURE WORKSPACE FOR WINDOWS

A Windows product focused on capturing notes, tasks and decisions from the edge of the screen without breaking the main workflow.

NAR-01 / CASE SPINE

Before the technical detail, read the problem, decision and evidence as one narrative chain.

01Problem
Fast capture, structured notes/tasks and the commercial model had to coexist without making the Windows experience heavy, while paid plans needed to be separated by real product differences.
02Decision
Keep an edge-first fast-access model instead of growing into a general-purpose desktop dashboard
03System architecture
Product and commercial architecture
04Build
Windows-first fast capture and Command Center product model
05Delivery
Rail's rail.ahmetcanal.com sales surface, pricing and Paddle plan configuration are in place, while the Windows product is explicitly kept in pre-release state in the source. This case focuses on product boundaries and commercial architecture.
06Evidence
Pre-release · actively developed · rail.ahmetcanal.com
07Learning
In a desktop productivity product, speed is a product boundary that comes before feature count.

STATUS: Pre-release · actively developed
TYPE: Product · Windows productivity
ROLE: Product and systems architecture · Windows workflow and interaction model
PLATFORMS: Windows · Web sales surface

OUT-VERIFY / CASE / BUSINESS IMPACTPRJ-10

What was the problem, what changed, what is different now?

Before the technology details, this shows the transformation: the original bottleneck, the intervention, and the outcome that can be verified today.

OUT-01

PROBLEM

Fast capture, structured notes/tasks and the commercial model had to coexist without making the Windows experience heavy, while paid plans needed to be separated by real product differences.

OUT-02

INTERVENTION

I positioned Rail as a Windows-first edge workspace, bringing Command Center, notes, tasks, folders, Markdown/Rich Text and global shortcuts into one fast-access model. Commercially, Cloud Sync remains the subscription differentiator while the lifetime license stays local-only.

OUT-03

OUTCOME / CURRENT STATE

Rail's rail.ahmetcanal.com sales surface, pricing and Paddle plan configuration are in place, while the Windows product is explicitly kept in pre-release state in the source. This case focuses on product boundaries and commercial architecture.

PROOF / LIVE SURFACE / DISTRIBUTION

EVD-01 / Current state: Pre-release · actively developed
EVD-02 / Live surface: https://rail.ahmetcanal.com
EVD-03 / Delivery surfaces: Windows · Web sales surface

ROI, revenue lift or percentages are shown only when a verifiable source exists. Otherwise the proof is the working product, distribution, system outcome and sourceable scope — never invented metrics.

CTX-01

Context

On desktop, capturing a small note or task often means leaving the current app, opening another window and switching context. Rail moves that micro-capture moment to the edge of the workspace instead of turning it into another heavy dashboard.

PRB-01

Problem

Fast capture, structured notes/tasks and the commercial model had to coexist without making the Windows experience heavy, while paid plans needed to be separated by real product differences.

ROL-01

My role

Product and systems architecture
Windows workflow and interaction model
Pricing, licensing and subscription architecture

SOL-01

Solution

BLD-01

What was built

Windows-first fast capture and Command Center product model
Notes, tasks, folders and Markdown / Rich Text surface
Global shortcuts and automatic-update product scope
Monthly and annual Rail Pro plans with a 7-day trial
Entitlement model reserving Cloud Sync for Pro subscriptions
One-time lifetime local license without Cloud Sync
Sales configuration wired to Paddle product / price identifiers

ARC-01

System architecture

Product and commercial architecture

SYS-TRACE READY

STK-01

Technical stack

WEB PRODUCT SURFACE

React 19 · TypeScript · TanStack Start · Tailwind CSS 4

BILLING / ENTITLEMENT

Paddle · Monthly Pro · Annual Pro · Lifetime Local

DELIVERY

Cloudflare · rail.ahmetcanal.com

PLATFORM

Windows

DEC-01

Important engineering decisions

Keep an edge-first fast-access model instead of growing into a general-purpose desktop dashboard
Make Cloud Sync the clear recurring value of the subscription
Avoid making lifetime a clone of the subscription; keep it limited to local features
Keep pre-release status distinct from a live-product claim

CODE-01

Code / architecture excerpts

Plan separationTS

01const railPlans = {
02  subscription: {
03    localFeatures: true,
04    cloudSync: true,
05  },
06  lifetime: {
07    localFeatures: true,
08    cloudSync: false,
09  },
10} as const;

FLOW-01

Data flow

Plan and entitlement flow

SYS-TRACE READY

RISK-01

Challenges and constraints

Growing notes, tasks and editing features without losing the fast-access feel
Creating a real, understandable product boundary between lifetime and subscription plans

OUT-01

Result / current state

LRN-01

Engineering takeaways

In a desktop productivity product, speed is a product boundary that comes before feature count.
A subscription is defensible when it is separated by a capability that carries recurring cost or recurring value.
For a pre-release product, proof should come from working product and commercial contracts, not invented usage metrics.

OUT-LIVE / VISIT PRODUCT