Engineering
280 hours planned
40h capacity gap
Sail
Your data.
Your data.
Your people.
Your agents.
Working together.
Connect your systems. Ask questions, understand what’s happening and act on it. We build the application around the way your business works.
Connected systems. Useful applications.
Workspace and Studio
Build the application. Work alongside the agent.
Your team works in views built for its jobs. In Studio, connect systems, define data stores and compose agents with checks and human decisions. Try editing the deal deck below. Each part is its own block.
Open deals
24From deal recordsNeeds review
6From review queueReady to sign
8From contractsDeal deck
| Account | Value | Next action |
|---|---|---|
| Northstar | $48,000 | Review terms |
| Meridian | $32,000 | Ready |
| Atlas | $16,000 | Confirm scope |
The agent needs a decision
A discount is outside the agreed range. Review it before the agent continues.
Workforce planning and scenarios
Build the plan around the people and work.
Resourcing and scenario modeling are applications built in Sail. Connect demand, skills, availability and budgets. Compare a hire, an internal move or a different start date, then bring the decision back to the people responsible.
01 / Connected systems
Connect the systems
your business runs on.
Connect projects in Jira, plans in NetSuite and customer records in Salesforce. Give your people and agents the context to work across them.
Explore integrations ↗
Jira Available 
Asana Discuss setup 
Linear Available 
NetSuite ERP Discuss setup 
SAP S/4HANA Discuss setup 
Salesforce Discuss setup 
ServiceNow Discuss setup 
Workday Available 
Oracle Fusion ERP Discuss setup 
Dynamics 365 Finance Discuss setup 
Snowflake Discuss setup 
Databricks Discuss setup Your systems
People, projects and costs
Connected in Sail
The records and their relationships
Your application
Plans, reports and decisions
02 / Analytics
See what needs
your attention.
Compare the plan with what’s happening. See where a team is short of capacity, a budget has changed or a decision needs review.
We build the measures around your process, with the records behind each figure available to check.
Plan your workforce ↗ Delivery capacity Next week
48h
Capacity gaps to resolve
2
Plans need review
Available hours Planned hours
Engineering 280h planned / 240h available
Operations 144h planned / 160h available
Customer support 88h planned / 80h available
Capacity gaps are assessed by team. Spare hours in another team don’t imply the right skills are available.
03 / Query with Eddy
Ask about the work.
Check the answer.
Ask Eddy a question about the information in Sail. Follow the answer back to the records it used, then decide what to do next.
Find a capacity gap, compare changes or investigate a figure without preparing a separate report first.
Meet Eddy ↗
Eddy / Delivery planning
Engineering has 240 hours available and 280 hours planned next week. Customer support needs another 8 hours. Review those gaps with the team leads before committing the work.
48h Capacity gaps across two teams
Based on Team availabilityDelivery plan
Engineering and Customer support have plans waiting for review. Both have more work planned than available capacity. Operations has an approved plan.
2 Team plans awaiting review
Based on Approval recordsTeam capacity
Engineering’s planned work increased from 240 to 280 hours. Customer support increased from 80 to 88 hours. The Operations plan remains at 144 hours.
+48h Additional work in the current plan
Based on Current planPrevious plan
04 / Views for your application
The same information.
The view your job needs.
Finance needs the numbers. A team lead needs the plan. An approver needs the changes. Give each person a view with the information and actions their work calls for.
Delivery planning Next week
| Team | Available | Planned | Plan status |
|---|---|---|---|
| Engineering | 240h | 280h | Needs review |
| Operations | 160h | 144h | Approved |
| Customer support | 80h | 88h | Needs review |
Needs review 2
Customer support
88 hours planned
8h capacity gapApproved 1
Operations
144 hours planned
Within available capacity Engineering 240h available · 280h planned
Operations 160h available · 144h planned
Customer support 80h available · 88h planned
One set of records. Different views for the people doing the work.
Tables for reviewing records Boards for decisions and approvals Charts for comparing plans
Built with your team
From the first connection
to the work you do every day.
We work with your team to connect the data, build the workflow and design its views. Permissions, approvals and exceptions are part of the application.
Start with one process. Measure what changes, then keep improving it as your business changes.
Find your use case ↗
Bring the process.
We’ll build it with you.
Talk about Sail ↗
Practical questions
What to know before you start.
Is Sail a workflow builder or an application platform?
Sail combines agents and workflows with connections, data stores, views and input forms. Studio is where the application is built. Workspace is where people use it, review the output and make decisions.
What happens when an agent needs a person?
The flow saves its progress and asks for the required input. Once the person responds, it can continue from that step with the decision attached. A long wait does not need to keep a model generating.
Where do workforce planning and scenario modeling fit?
They are applications built in Sail. Connect demand, availability, skills and budgets, compare alternative plans and keep assumptions separate from approved allocations.