Soil — customer commitments through delivery
Soil is built by Kartik Malhotra. It helps B2B software teams record a customer promise, assign an owner and deadline, review the work behind it and separately confirm customer delivery.
The product problem
A completed engineering task does not prove a customer received what was promised. Teams need a commitment record that stays visible through review and delivery confirmation.
Implemented capabilities
- Workspace accounts, manual commitments, owners and due dates.
- Review of candidates from selected Slack messages and links to accessible work.
- Rule-based checks for approaching deadlines, blocked work and stale evidence.
- Source-access checks, human approval for external actions and recorded action history.
- Application persistence in PostgreSQL, with tests covering workflows and permission boundaries.
Technical approach
Python and FastAPI serve the application. Jinja and htmx provide the interface; PostgreSQL holds workspace and workflow records. Rules handle core commitment tracking. Optional model-assisted answers and drafts sit alongside the workflow.
- Record or reviewA manual promise or a candidate from an authorised source.
- Check evidenceOwner, deadline and explicitly linked work within access boundaries.
- Confirm deliveryA person reviews evidence and records what reached the customer.
What you can inspect
The public product site and its fictional commitment demo are available without connecting your tools. The source implementation and deployed version were reviewed for this description.
Current limits
The public demo uses fictional data. Connected evidence depends on provider access and configuration; not every advertised workspace view is the same as a verified end-to-end integration. Core commitment tracking does not require an AI model. This page makes no claim about customer adoption, paid-client outcomes, revenue or production performance.
Visit Soil ↗ · Discuss an integration or workflow like this →