Use cases
Start with the process. Then the agent.
The first week is in the org, reading what already exists. The honest no: if the work is a software factory with a named delivery date, we are the wrong partner.
- 01Models · Claude, Gemini, OpenAI, Bedrock
- 02Agents · Agentforce, CrewAI, ADK, A2A
- 03Memory · Neo4j, Cognee, RAG
- 04Identity · IndyKite, SSO, entitlements
- 05Governance · policy, audit, human override
Use cases
Find the process that sounds like your week.
Open the one that matches the work. Each card says where it runs: Slack, WhatsApp or Salesforce. Search for Slack to see the Slack AI agents, including Agentforce in Slack and Claude in Slack. If none fit, clear the cut and tell us the process.
New100 decisions a System One model can take off your LLM bill. Ranked by the model itself.
- SalesAI Sales Pipeline AutomationA pipeline the desk can trust. Lead scoring, opportunity tracking, and a forecast built from the org, not a side spreadsheet.Runs in: Salesforce, Slack
- OperationsAI Customer Service TransformationCases, knowledge, and the channel the customer already uses. An agent on the repeats. A person on the exceptions.Runs in: Salesforce, WhatsApp, Slack
- FinanceFinancial reportingClose, statements, and a pack finance can run without a rebuild. Salesforce plus the finance system of record.Runs in: Salesforce
- MarketingMarketing campaignsJourneys on a customer the org already knows. Consent first. Marketing Cloud when the send can stand behind the list.Runs in: Salesforce
- HRHR onboardingA named onboarding desk. Documents, access, and a reviewer on the exceptions. Not a $7,000-per-hire slide.Runs in: Slack
- ITAI IT Support TransformationTicket routing and a knowledge desk. An agent on the repeats. A person on the exceptions.Runs in: Slack, Salesforce
- LegalLegal document reviewContracts as a desk. Review, redline, and a lawyer on the exceptions. We will not invent a 209% ROI.
- OperationsSupply chainInventory and orders between ERP and Salesforce when that is the job. Real-time or batch from the desk.Runs in: Salesforce
- DataData analyticsA view on records the org already trusts. Tableau or the CRM report after the duplicates are gone.Runs in: Salesforce
- ComplianceCompliance monitoringAudit, consent, and a trail that travels with the record. We will not invent avoided-penalty euros.Runs in: Salesforce
- Product DevelopmentProduct developmentA named R&D desk. Requirements, reviews, and a person on the exceptions. Not a $50M savings slide.
- OperationsInventory managementStock as a desk between ERP and Salesforce. Accuracy after the mapping is owned.Runs in: Salesforce
- FinanceInvoice processingAccounts payable as a process, not a folder of PDFs. Capture, match, and a person on the exception.
- MarketingContent creationA content desk with a reviewer. Scale after the voice is named. Not a 42x email ROI.
- Quality AssuranceQuality assuranceA test desk. Coverage you can name. A person on the defect that matters. Not a 675% ROI.
- HRRecruitment screeningA hiring desk. Screen against a written role. A person on the shortlist. Not a 3x quality-of-hire slide.
- OperationsMeeting schedulingCalendar as a desk. The inbox the team already uses. A person on the exception.
- FinanceExpense reportsCapture, policy, and approval on a named desk. We will not invent a 500% ROI or a sterling fraud number.Runs in: Slack
- MarketingSocial media operationsA social desk. Queue, reply, and a person on the brand voice. Not a 753% revenue slide.
- LegalContract managementContract lifecycle as a desk. Intake, review, and a lawyer on the exception. Not a $2.2M breach slide.
- Government ServicesGolden Visa screeningEligibility as a named desk. Documents, rules, and a reviewer. We will not invent an annual euro savings.
- Health CampaignsHealth awarenessA public-health desk. Content, language, and a reviewer. We will not invent AED 15M or 2.8M residents.
- Cultural PreservationCultural heritage guideA heritage desk. Guides, languages, and a reviewer. We will not invent AED 15M or 2.8M residents.
- OperationsFirst processA repetitive, documented job tied to revenue. We set up one agent on that process and keep a reviewer on the exceptions.Runs in: Salesforce, Slack, WhatsApp
- SalesBook of businessPull policy data from the last system into yours. Insurance and brokerage books. UAE and US teams buy this.Runs in: Salesforce
- OperationsWhatsApp for customers, Slack for the companyCustomers write on WhatsApp and your team answers from Slack, so the same question is retyped twice. One agent job runs in both, with the record in Salesforce.Runs in: WhatsApp, Slack, Salesforce
- SalesAgentforce in SlackYour team asks Salesforce questions in Slack and waits for someone with a licence to look. Agentforce answers in the channel from the record, and a person approves the update in the thread.Runs in: Slack, Salesforce
- OperationsClaude in SlackWork that spans documents, tickets and other tools gets passed around in DMs. Claude joins the channel as a shared teammate on one named job, and the whole team sees what it did.Runs in: Slack
How we work
From use case to production.
- 01Week 1 in the orgWe read what already exists before anyone adds a cloud.
- 02Written noteWhat is worth fixing, what is worth finishing, and what is not. Not a dashboard.
- 03Fixed scope and priceWe can fix-price a named, scoped piece once the process is clear. We will not fix-price a rescue we have not assessed.
- 04BuildWe implement around the process you already run.
- 05We stayAfter go-live, a person stays on the exceptions.
The brief
Tell us which one is yours.
One email starts it. We ask about the use case and the object after.