Pencel Turns Business Outcomes Into Agentic Workflows That Run Reliably
Bo Wang, Founder and CEO
Press Release
Pencel connects the systems a business already runs on, learns how that business operates, and turns recurring processes into governed AI workflows owners can trust. It is the Cursor moment for business users.
SEATTLE, August 1, 2026 — Pencel today launched an AI operations system for small and mid-market businesses that want AI to get real work done inside their own environment. Pencel curates a company's unique context and standard operating procedures (SOPs), so AI understands how the business runs. Business owners juggle too many disconnected tools. Pencel unifies the information scattered across CRM, ERP, accounting, logistics, and internal communication systems, then lets non-technical users turn daily routines into workflows. Built on the world's first AI compiler for workflow development and orchestration, Pencel is designed for trust, reliability, and ease of use. Every workflow runs inside permissions the company sets, pauses for human approval where required, and leaves an auditable record. Pencel turns a business into an AI-native company that moves faster and adapts quicker.
Customer Problem
Fragmented Software: Most growing companies don't lack software. They own too much software that doesn't work together. Sales information lives in a CRM, financial records in accounting software, operating details in industry-specific systems, and company procedures on employees' laptops. People fill the gaps themselves, holding the pieces in their heads and stitching information together by hand. The same problem repeats at every company, every day, draining productivity and slowing both operations and decision making.
Missing Business Context: AI models grow smarter every day, yet most business users report little productivity gain. A general AI assistant does not know a company's products, policies, priorities, procedures, pricing rules, or past decisions unless the user supplies that context every time. The model may be intelligent, but it is a stranger to the business.
Agentic Workflow Is Not Reliable: Companies run on workflows that stitch together their daily operations. Traditional Robotic Process Automation (RPA) tools are reliable, but they are difficult to build and too rigid to handle ambiguity. AI agents, by contrast, can understand business semantics and make judgments, but their non-deterministic behavior makes them hard to trust when stakes are high. Companies are forced to choose between automation that can't think and intelligence they can't govern.
Ease of Use for Business Users: Nearly every agent product on the market is built for someone who already understands prompts, skills, tools, harnesses, and evals. Business users should not have to learn how an agent works to get an agent to work. In summary, fragmented systems, missing business context, lack of trust in agentic workflows, and poor ease of use remain the biggest blockers to adopting AI agents to transform enterprise productivity.
The Solution
Pencel first connects the systems and knowledge a company already uses, then turns them into a shared foundation for AI-powered work. A company keeps its CRM, accounting software, document system, and industry applications as the systems of record. Pencel coordinates work across them through secure, permissioned, one-click integrations. The company also gives Pencel the operating context each workflow needs: procedures, product information, customer escalations, and compliance policies. On top of these systems of record, Pencel builds a system of intelligence, a semantic and reasoning layer that understands the business.
A business user starts with the outcome, not the agent technology. Building an agent normally demands a steep learning curve to make it behave properly and safely, which can be intimidating for business users. Pencel removes the burden entirely. Through a collaborative, interactive conversation, Pencel gathers the desired outcome and requirements. Pencel developed an AI-compiler-based agentic workflow runtime that translates them into a structured workflow defining which systems the agent may access, which steps it must complete, and where human approval is required. The compiled plan gives the agent clear instructions, tools, and policies, so it stays in its lane during execution. For an AI startup in Seattle, Pencel built an RFP workflow that monitors procurement sources, evaluates each opportunity against the company's qualification criteria, and prepares a proposal from approved materials. When the workflow hits a judgment call or an exception, it stops and asks. The user focuses on the outcome and reviews the quality of the results, and Pencel does the rest.
Users review results in Pulse, Pencel's personalized operations feed. Pulse works like a chief of staff, continuously preparing the information and decisions most relevant to each user. Each card represents the result of a workflow the user created or approved. It explains what happened and stages the next action. An email card, for example, includes a response drafted from the company's context and the user's writing preferences. This closed loop is a Pencel design tenet: every piece of information should be actionable, not just nice to know. Pencel's built-in memory system learns from every user action and saves the important signals, so answers and workflows get better and more personalized with use.
The Pencel agentic system is not only for personal productivity. It is built for teams. Users share workflows, knowledge, and agents with colleagues, all governed by access controls, so a routine workflow keeps running even when its owner is on vacation. Teams can share SOPs and compliance policies in one place and use them to onboard new members quickly and retain knowledge through employee attrition.
Pencel builds control, transparency, and security into every step, so a business can run workflows with peace of mind. The customer decides what each workflow may access, what actions it may take, and where human approval is required. A company can require review before Pencel sends an external message, changes a financial record, or takes any other high-impact action. Each run creates an evidence record showing which sources Pencel consulted, which tools it used, which actions it took, and which outputs it produced.
From the Founder
"The next generation of companies will run on an AI-native operating layer that connects people, knowledge, and work, and that layer keeps learning and gets better every week it's used," said Bo Wang, founder and CEO of Pencel. "Most agentic tools still require technical knowledge to get a high-quality outcome and to use agents safely. Pencel is built to let business users achieve more without worrying about the technical details of building and managing an agent. Business users should just focus on the outcome, and the agentic system should just work."
Getting Started
Individuals can download Pencel at pencel.ai/download to improve their personal productivity.
For companies, Pencel is running a design-partner program with early customers in logistics, fintech, and AI. Design partners receive hands-on support and workflows built around their business. Contact partners@pencel.ai to join.
Frequently Asked Questions
What is Pencel, concretely?
A desktop application. You install it on macOS or Windows (a Linux build is also available), and your workspace lives on your machine: your workflows, your knowledge, your run history, your memory. It is not a browser tab that holds your business in someone else's database.
Why should I use Pencel? What makes it different from other AI products?
Five things. Each one exists somewhere else in some form. The combination is what no other product gives you.
It already knows your business. Your SOPs, product details, pricing rules, policies, and past decisions live in Pencel as durable context, not as something you paste into a chat box every morning. Its memory keeps learning from what you accept, reject, and edit, so the output gets closer to what you actually want each week.
Work is defined as a plan you approve, not a prompt you hope lands. You describe an outcome in business language. Pencel compiles it into an explicit workflow naming the systems it may touch, the steps it must complete, and the points where it must stop for a human. You approve that plan once, before anything runs.
It acts inside your systems, not beside them. One-click permissioned integrations mean a workflow can read the CRM, post to accounting, and send the email, rather than producing text you then re-key into four tools by hand.
It runs without you, then brings you the decisions. Workflows run on a schedule. Results arrive in Pulse as cards that explain what happened and stage the next action, so your morning starts with decisions to make instead of systems to check.
It runs on your machine. Your workspace, run history, and memory are local. Your systems of record stay under your control.
The value shows up in the combination. A workflow that knows your escalation policy, is permitted to touch your CRM, runs at 7am Monday without being asked, stops when it hits a decision only you should make, and leaves a record you can audit afterward. Products that do one of those are common. Doing all five together is the product.
How is this different from ChatGPT or Claude?
A general assistant starts every conversation as a stranger. It doesn't know your pricing rules, your escalation policy, your customers, or what you decided last quarter, so you re-explain your business every time, and the quality of the answer depends on how much context you had the patience to type.
Pencel is built the other way around. You give it your operating context once, including SOPs, product information, policies, and past decisions, and connect the systems that hold the rest. Then it can run on a schedule, take actions in those systems within permissions you set, and remember what happened. The difference isn't the model. It's everything around the model.
How is it different from Zapier, n8n, or RPA?
Those tools are deterministic, which is their strength and their ceiling. You have to specify every branch in advance, and the automation breaks the moment reality doesn't match the diagram. That's why so much of the work that actually matters never gets automated: it involves judgment.
Agents can handle the judgment but are hard to trust, because nothing constrains what they'll do. Pencel's answer is to compile your intent into a structured plan first, naming which systems the agent may touch, which steps it must complete, and where it must stop and ask a human. The agent still reasons. It just reasons inside a boundary you approved.
What is the AI compiler, and why does it matter?
It is what makes an agent safe enough to leave running unattended.
Every agent product has to answer one question: what stops this thing from doing something you didn't want? Most answers are some form of "a human watches it." That works when the human is an engineer reading a code diff. It does not work when the goal is a workflow that runs at 7am on Monday whether or not anyone is looking.
The compiler moves the review to the front. You describe the outcome in business language; Pencel lowers it into an explicit plan naming the tools, the data sources, the steps, and the approval gates. You approve that plan once. Every run afterward executes inside it. Contradictions and missing pieces surface at compile time rather than halfway through a live run against your production systems.
| Built for | How work gets defined | What limits what it can do | |
|---|---|---|---|
| ChatGPT / Claude | Anyone, one conversation at a time | You retype the context each session | Nothing needed: it can't reach your systems |
| Claude Code / Cursor | Engineers | You supervise turn by turn and read the diff | Your review of every proposed change |
| Zapier / n8n / RPA | Technical ops builders | You draw every branch in advance | The diagram, which also caps what it can handle |
| Pencel | Business users | You state the outcome; Pencel compiles a plan you approve | The approved plan: named tools, data, and approval gates |
The comparison with coding agents is the instructive one. Claude Code is excellent at what it does, but its safety model is an expert reviewing each change as it happens. That is a fine trade when the reviewer can read code and the work is happening in front of them. It is the wrong trade for a sales ops manager who wants quotes drafted overnight.
Pencel puts the boundary in a different place. The constraint is checked before the run, not during it, which is what makes unattended execution reasonable. And you never see a prompt, a tool schema, or an eval. You see the plan, in business language, and you approve it.
Do I need to know anything about agents or prompting?
No. That's the design constraint the whole product is built under. If a business user has to learn what a tool harness is to get their Monday report automated, we've failed.
What happens when the agent gets something wrong?
Three things are in place. We'd rather say plainly that all three matter, because none of them is sufficient alone.
Permissions. Each workflow can only reach the systems you granted it.
Approval gates. You can require human review before any high-impact action: sending an external message, changing a financial record, spending money. The workflow pauses and waits for you.
Evidence records. Every run leaves a trace of which sources were consulted, which tools ran, which actions were taken, and what was produced. When something looks wrong, you can see exactly how it got there instead of guessing.
The honest version: agents make mistakes. The design goal isn't zero mistakes. It's that no mistake reaches the outside world without a human seeing it first, and that every mistake is diagnosable afterward.
What can Pencel connect to?
Integrations are built on the Model Context Protocol, so the set keeps growing. Today that includes Google Workspace and Gmail, Slack, Notion, GitHub, Stripe, QuickBooks, Linear, Atlassian, Asana, web search and scraping, and direct database connections including PostgreSQL and SQLite, plus your local filesystem. Industry-specific and internal systems can be connected through custom MCP servers.
Where does my data live?
Your workspace is stored locally on your machine. Your systems of record stay yours. Pencel coordinates across them; it doesn't absorb them.
Model inference is the one thing that necessarily leaves your machine, and you choose how. Bring your own API key and prompts go directly from your machine to Anthropic, OpenAI, or Google. Use Pencel's managed credits and requests route through our proxy to those same providers over encrypted connections; we don't log your prompt content. See the privacy policy for specifics.
Does it work for a team, or just one person?
Both. Workflows, knowledge, and agents can be shared with colleagues under access controls. That is what keeps a recurring workflow running when the person who built it is on vacation, and what turns one employee's undocumented process into something the team owns. Shared SOPs and policies also make onboarding faster and reduce what you lose when someone leaves.
What does it cost?
The Free plan is the full local desktop experience with your own API keys, and no credit card. Pro Desktop is $49/month (or $468/year) and includes managed AI credits, so there are no keys to set up. Enterprise is custom, for teams that need shared workspaces, pooled credits, and role-based access. Full detail on the pricing page.
What is Pencel not good at yet?
Fair question to ask of anything that claims to run your operations.
Pencel is only as good as the context you give it. A workflow built on thin or stale knowledge produces confident, wrong output: the same failure mode as a new hire who was never trained. The setup work is real, and we'd rather say so than pretend the product reads your mind.
It's also aimed at recurring, describable processes. If a task is genuinely novel every time, a workflow is the wrong shape for it. Use Pencel conversationally instead and skip the compile.
And workflows that touch consequential systems will stop and ask you more often than you might expect. That's deliberate, not a rough edge. We'd rather be interrupted than surprised.
How do I get started?
Download Pencel and build your first workflow. The free plan is enough to see whether this works for you. If you're a company that wants workflows built around your operations with hands-on support, our design-partner program is open in logistics, fintech, and AI: partners@pencel.ai.