Runner turns the accounts you already use into a day already in order.
Connect GitHub once to give Runner the shape of your product. Once Google completes its verification, Google Calendar brings every meeting into My Day and Gmail keeps every email in its familiar address and thread.
Your product, already taking shape
Connect GitHub and Runner reads your repository step by step: what you sell, a first guess at who it's for, and your brand colour. On the model you connect, it proposes a growth team and a plan for how the product wins.
- Watch it buildConnecting, or starting a build yourself, begins a run you can follow step by step. Each run is kept with its date and the commit it started from, and the latest shows every step and what it produced.
- Start with decisions, not setupWhat you sell and who it's for arrive as editable proposals. Confirm what fits; a later build never replaces a product type or customer profile you confirmed.
- Keep what it learned in your repositoryDownload it as a RUNNER.md anyone can read and a .runner/ folder any tool can parse. Commit them, and the next build reads back the product’s name, type and who it prospects, and shows you where they differ.
Runner reads your default branch, your Markdown and text files included, and takes dependency names without their versions and configuration keys without their values. A committed .env is never fetched, and the planning steps send a model names and paths plus short excerpts of your README and other Markdown at the root or in docs/, never commit messages.
Why your code stays yours
Runner re-reads a connected repository on a schedule to keep what it knows current, and nothing on that schedule calls a model: the planning steps run only when you ask for them. Apart from your brand colour, it decides nothing: when neither this product nor your organization has one, Runner takes it from your stylesheet, and the product’s workspace, emails and embeds use it. Your product type is not set until you press Set product type. A model may only name a product type Runner already has, with the evidence behind it shown beside it, and you apply it or leave it. The planning steps get names and paths from your repository and short excerpts of its README and other Markdown at the root or in docs/; if one of them holds an email address, or a phone number, key or token in a format Runner recognises, the excerpts are withheld whole. Commit messages are never sent. Your Markdown and text files become knowledge an agent may quote when it answers a question. Runner’s GitHub App reads your repository. Where an admin allows it, Runner proposes what it learned as a pull request on its own branch; it never pushes to your branches, and merging stays your call.
fernhollow/orchard-billing
PublicmainSignals Runner found
- instruction files
- dependency names
- configuration keys
- an accent colour
Runner reads your default branch: its file paths and latest commit, dependency names without their versions, configuration keys without their values, your Markdown and text files, and your stylesheet's accent colour. A committed .env is never fetched, and the planning steps send a model names and paths plus short excerpts of your README and other Markdown at the root or in docs/, never commit messages.
Your project
Suggestions ready to review
- Product typeStrong match
- Direct commerceFrom a dependency name
- Instructions in effect1 open conflict
- One file governs the root, another its own directoryFrom your instruction files
- Brand colourApplied, and yours to change
- Taken from your own stylesFrom a stylesheet
- How this product winsReady for your review
- Three phases, every step linked to its pageFrom the model you connected, at this commit
Your product begins to take shape
Runner suggests what you sell, showing where it got that, and a first guess at who it's for. Neither becomes your product's until you confirm it, and if your code says too little, Runner's rules say so and suggest nothing.
Your team's instructions come with it
Every sync maps each instruction file to the part of the repository it guides. When two clash, Runner shows you both instead of choosing — and what they say is never treated as permission.
Your customer, a team and a plan, ready to review
On the model you connect, Runner drafts a portrait of who you sell to, each customer type citing its evidence, proposes a growth team, and lays out a phased plan for how your product wins. All three are yours to review, and nothing launches until an admin approves it.
It even feels like your product
Runner carries in the brand colour it finds when you connect, for the workspace, emails and embeds, and never over a colour you or your organization already chose. If it cannot find one, it says it picked rather than claiming a match.
Walk in knowing where the day starts
Today's meetings arrive in My Day beside the next actions and work Runner already has moving. Open one view and know where your attention matters.
- Your day stays yoursEach person connects their own calendar, so everyone in the workspace opens a day arranged around their own meetings.
- Your calendar becomes useful contextRunner reads the relevant window from your primary calendar and puts each meeting beside the account, brief and next action it belongs to. It is a reader — nothing here creates, moves or cancels an event.
Google Calendar connects once Google completes its verification. Calendar access is personal and read-only, and Runner gives each meeting the account context that helps you walk in prepared.
Keep every message unmistakably yours
Write the campaign or reply in Runner. It leaves from the Gmail address your customers know, stays in the thread and appears in Sent. To them, it is simply you.
- Send from the account people knowCampaigns and replies leave from your Gmail address and appear in Sent with the rest of your work. Connecting Gmail to send asks for exactly that and nothing more — Runner never reads the mailbox on it.
- Bring replies back to the same recordA separate inbox connection lets Runner place replies beside the customer, campaign and next action they belong to.
Gmail connects once Google completes its verification. Sending and inbox access are two separate connections, so you choose exactly what Runner can do with your mail.
Connect once. Start every day ahead.
Create your account and pick a plan to start.
Build my team