For independent consultants, fractional executives and owner-operators — dates promised to clients, days cut up by other people's meetings.
The planner that learns how long your work actually takes.
You decide what is a commitment. A deterministic engine decides where it goes and says why — and every week it knows your work better. The models only read and write words; they never move your schedule.
Three things it does differently
- Every sitting says why it is where it is.
- Not “the AI decided”. Each hour the plan books stores the factors it was placed from and says them back beside the sitting: “Placed at the first free time after the 9:30–10:00 meeting and its 10-minute padding.”
- An overcommitted day reads 164%. The number is never capped.
- Work that does not fit is listed with the reason it found no place, never dropped, never squeezed in. Assumed hours say “assumed” until you confirm them.
- Plans hold still.
- A sitting within ninety minutes never reshuffles without a real conflict, and a repair moves the minimum. When a meeting lands on a planned morning, only the hour it displaced moves, and the plan says what moved and why.
A day, as it plans one
- 9:00 – 9:30Reply to the tender threadPlaced at the first free minute when the plan was made.
- 9:30 – 10:00Stand-upfrom your calendar
- 10:10 – 11:10Review the contractPlaced at the first free time after the 9:30–10:00 meeting and its 10-minute padding. Given early capacity so its hard deadline stays possible.
- 12:00 – 13:00Lunch
- 13:00 – 14:00Client callfrom your calendar
- 14:10 – 15:45Draft the proposalPlaced at the first free time after the 13:00–14:00 meeting and its 10-minute padding. Its work was sized at 1h 32m when placed: 1h of your estimate × deep work's ×1.52 (7 samples, 30% starting assumption).
Found no place: Prepare the board pack (2h) — no room on the day you committed to, nor on the two working days after it that this plan reaches. Do it anyway pins it where you say.
An example day. The sentences are the product's own; the day is made up.
The close is a two-minute conversation
Every evening the day is judged against the plan it started with, from the record — the timer, the tracker, what you marked done — and said in one line, which the next morning's door repeats:
Plan kept today: 3 of 5 sittings (2h 40m of 4h 30m) — 1 moved by you, 1 missed.
Then the day's open loops answered for, what the next working day holds first, and a note read for commitments. No mood check-in, no score, no streak. What you answer feeds the learning; what you skip is still on the record as time the tracker saw with no task named.
Every week it knows your work better — here is the founder's own record
The one chart this claim rests on, live from the account this was built in. Each week: what the work took over what was sized for it — the first guess, and the plan's sizing of that guess with what the learning knew when the week began, replayed from the record. Aggregate ratios only; no task is named.
| Week | Measured tasks | Took over the founder's first guess | Took over the plan's sizing |
|---|---|---|---|
| 17 Aug | 6 | ×1.07 | ×1.07 |
| 24 Aug | 6 | ×0.80 | ×0.80 |
| 31 Aug | 13 | ×1.46 | ×1.39 |
| 7 Sep | 15 | ×2.35 | ×2.10 |
| 14 Sep | 14 | ×1.56 | ×1.44 |
| 21 Sep | 7 | ×1.18 | ×1.05 |
| 28 Sep | 6 | ×1.36 | ×1.11 |
| 5 Oct | 5 | ×2.17 | ×1.90 |
| 12 Oct | 5 | ×1.17 | ×1.08 |
| 19 Oct so far | 1 (under three: no verdict) | ×1.67 | ×1.03 |
the plan's sizing, with what it knew when the week beganthe founder's first guess×1 is what the work took; faint is a week with under three measured tasks, which counts in no figure
Over 9 weeks with 3 or more measured tasks (77 tasks), the founder's first guesses were off by 55% of what the work took, and the plan's sizing by 52%. The plan's sizing was fewer minutes off than the first guess in 6 of 7 such weeks with a record to size by.
The latest week with 3 or more measured tasks was sized 57% from the record and 43% from the starting assumption, 12% of its guessed minutes being work with no kind, which is ×1 whatever the record. Regenerated about every fifteen minutes.
Privacy, in the policy's own words
- The desktop app records which application has focus and how long — never a window title, never anything you typed or read. Site names only if you switch them on, and then the domain alone.
- It never modifies or deletes your own calendar events. It reads them, and writes only to a separate calendar it creates for you; there is a mode where no meeting title is ever stored.
- Models read messy text and write summaries. Placement, priority and repair are plain deterministic code. Your browsing domains are never sent to any model at all.
- Settings has a delete button, and it is not a request: everything the app stores goes at once, and the sign-in record is removed by hand, which the policy says plainly. No advertising trackers, no analytics scripts.
The whole of it, written from the data model rather than a template: the privacy policy.
What it will cost
- One plan, billed yearly
- $16 a month
- Month to month
- $20 a month
- Founding price, the first 100 people — held for as long as you stay
- $12 a month, yearly
- Trial
- 30 days, no card
The models cost real money per account, so every account has a spending ceiling, stated in the terms; the price is set so a heavy month stays inside it. Cancelling will be as plain as deleting. Nothing can be bought yet — the beta is closed, and the first invitations go to the waitlist.
Get in
Invitations go out a few at a time, by hand, with a twenty-minute call to set up your hours and your first plan. Leave an address and nothing else.
Already invited? Sign in. Curious how it works, in full? What this is.
The web app is the product. The optional Windows companion — Intenday 0.3.1 for Windows — adds the tracker, the capture hotkey and the floating timer. It is offered in Settings; Windows warns that the publisher is unknown until the installer is signed.