Perch

Perch is being built to equip an agent to be an effective executive or assistant. The agent supplies the reasoning; Perch supplies a persistent workspace, integrated administrative workflows, and the context to carry work forward across conversations and runtimes.

The first working slice is project continuity: objectives, decisions, constraints, evidence and open questions remain distinct. Start with one authorized project, capture a decision with its source, and leave the next useful step alongside the evidence it needs. A hypothesis should never silently become a verified fact.

Calendars, contacts, mail, tasks and commitments, notes and documents are planned integrations with shared providers. Perch connects the office experience; it does not become a competing calendar, contact list or task database. Existing tools and future O+K-native providers should both fit below that experience.

Marketing and acquisition belong to a separate marketing product. Perch can help an assistant handle a qualified opportunity, prepare a meeting and follow through, without owning campaign targeting, outreach or the sales pipeline.

On the next session, review the current project model, check unresolved questions, and choose the next useful step. The first acceptance test is Perch managing its own handoff without Jon retelling the conversation. Planned integrations are not evidence of a connected provider or permission to act.

Perch is designed to work with different agents through MCP and a context API. Identity, grants, source and deployment authority remain with their existing owners. Remembering an instruction is not permission to execute it, and access must remain scoped to the project.

Today this is an internal preview. Source integration and release qualification are in progress; a public hosted service and customer onboarding are not yet accepted. Not open for public signup. Pricing is not announced, and there is no paid plan or free-trial promise on this page.