Sherpa today
For each function, the control plane shows what’s happening and what needs a decision. Agents help do the work, from building software to preparing customer follow-ups and explaining the numbers.
Open an item to see the details and the decision needed.
Illustrative product view using example records.
You should be able to see where the work stands.
Plans, work, and decisions often end up in different tools and conversations. Sherpa brings those records together so you can pick up where you left off.What is built
We’ve built three modules around engineering, go-to-market, and finance. Each has its own workflows and agents, and you can review the work in one place.
Plan the work, build it with a coding assistant, and check what is ready to release.
Keep the history of a relationship, prepare the next conversation, and follow through on what you’ve promised.
Review costs and revenue, check the underlying records, and work through the questions before closing a period.
Inside the product
The control plane is where you review the work. Agents prepare or carry out tasks within each function, with decisions and approvals recorded as you go.
See what’s been built, what has been checked, and what needs your decision.
Review projects, work items, blockers, decisions, and release checks. See whether the connected sources are up to date.Open the records behind a status to see how it was reached.
Use Sherpa’s skills in your coding assistant to plan and build software, investigate issues, run checks, and record what was learned.The assistant works from the agreed plan and follows the steps for review and release.
Agree the scope, resolve choices that affect the work, and approve releases at the appropriate stage.
The Engineering agent works in your coding assistant. The control plane shows the resulting work, checks, and decisions.
Delivery review
Coding assistant handoff
The changes and check results are ready to review. The next step is integration into Development.
Illustrative example of the records in this module.
Use the history of a relationship to decide who to contact and what to say.
See people, past conversations, permission to contact them, recent public activity, and promises made.Review these details before preparing a message.
Suggest who may need attention and prepare a message or proposed commitment using the records you select.The suggestion shows which records it used and where it is uncertain.
Edit and approve the message, then choose to create the Gmail draft. Record what happened when a commitment is completed.
Sherpa creates the Gmail draft after your review. You send it from your mailbox.
Relationship follow-up
GTM agent preparation
Review the suggested message alongside the past conversation and the reason for following up.
Illustrative example of the records in this module.
Check the numbers, understand any gaps, and decide whether a period is ready to close.
Review costs, revenue, missing source data, expense categories, reconciliation, reports, and cash scenarios.Open the source records to check the numbers.
Explain differences, suggest categories, and summarize reports or cash scenarios using the records you select.Cash scenarios use your stated assumptions for the calculations. The agent explains the results.
Set the financial policies, apply the categories you’ve reviewed, resolve differences against the records, and close or reopen a period.
The Finance module supports review and reporting. It does not make payments, file taxes, or set up provider accounts.
Selected reporting period
Finance agent explanation
The explanation points to the billing records that need review. Check these and resolve the missing information before closing the period.
Illustrative example of the records in this module.
Sherpa’s plugins contain the skills and instructions for each function. The Engineering agent uses these in your coding assistant to plan, build, and check the work.
These agents use the records you select to prepare suggestions and explanations. They need an Agent Host and the relevant data connections set up before use.
The modules use the same sign-in, access controls, data connections, and activity history. You can review a proposed action before choosing whether to carry it out.
Where we are
The three modules are built and tested locally. We still need to verify the connections and agents with real accounts and see how each module holds up in everyday use.
The modules cover software delivery, relationship history and follow-ups, and financial review and reporting. Each can be used on its own once the relevant setup is complete.
The next step is to connect real accounts, verify that the agents work with them, and make each module reliable in day-to-day use.
Once the individual modules work well, we’ll connect them around company priorities, customer outcomes, and decisions about time and money.
The larger vision
Our view is that every company will build software and use AI agents, regardless of industry. Engineering, go-to-market, and finance are at the heart of that work.
We want Sherpa to connect these functions so founders and CEOs can see what is working, decide where to focus, and put time and money behind those decisions.
Tell us what you thinkA question we want Sherpa to answer
I’d like to hear from founders and CEOs about the problems this could solve for them. What would you use? What have we missed? That feedback will help us decide what to build next.