Est. 2019 · Austin, Texas
B2B workflow software that product and ops can both live in
Kiln is a workflow platform for B2B SaaS teams: pipeline CRM, approval routing, internal admin tools, and automations with a real API. Built in Austin for companies that have outgrown spreadsheets and underused the enterprise suite they already pay for.
How Kiln works
Revops, support, and product should not keep the same customer in three systems. Kiln is a workspace for pipeline, tickets, and internal tools with a shared object model. Sales can run a CRM. Engineering can attach webhooks, audit logs, and SSO without a six-month services project.
We sell product-led: a free workspace, usage-based automation runs, and a seat model that does not punish you for inviting the intern. Onboarding is a template library — inbound lead routing, churn save plays, vendor approvals — not a blank canvas and a prayer.
Teams evaluating Salesforce, HubSpot, Zendesk, and Monday.com often land here when they want one workflow graph, SQL-friendly exports, and an API that does not feel like a tax. We document like a developer tool because the buyers who stay are technical.
What we actually do
Pipeline CRM
Deals, companies, contacts, and custom objects. Forecast views that match how your VP actually runs Monday standup.
Workflow automation
Triggers, delays, branching, and human-in-the-loop steps. Idempotent runs you can replay after a bad deploy.
Internal tools
Admin screens on top of your objects: refunds, seat grants, feature flags. Less custom React, more governed actions.
Developer platform
REST, webhooks, TypeScript SDK, and audit trails. SCIM and SAML on the Growth plan.
Integrations
Stripe, Slack, Linear, HubSpot, and a generic HTTP connector. We would rather be the system of action than the system of everything.
Implementation
Two-week paid onboarding for teams migrating off a spreadsheet or a neglected Salesforce org. No multi-year SI circus.
Guides from the studio
These are the pieces we keep on the homepage because they are the questions people ask in the first meeting.
- 01
When to leave a horizontal CRM for a workflow graph
Signals you have outgrown undifferentiated Salesforce or HubSpot.
- 02
Product-led growth instrumentation that finance will trust
Activation events, expansion revenue, and a definition of paid that is not a vibe.
- 03
Building internal tools without a second frontend team
Object permissions, action logs, and why admin UIs rot.
- 04
Webhook design for SaaS: retries, signatures, and poison queues
The boring reliability work that keeps customer ops from paging you.
- 05
Seat-based vs usage-based pricing for B2B workflow tools
What we learned from automation-run billing in year one.
- 06
Revops handoff: lead routing that does not create shadow ops
Round robin, territory, and a single owner field.
- 07
Evaluating developer experience in a CRM API
Idempotency keys, list filters, and docs that include error bodies.
- 08
SOC 2 without pausing the product roadmap
Access reviews, change management, and what auditors actually sample.
The landscape we work in
Kiln is not these publications — we read them, send clients to them, and sit in the same niche. If you already follow this beat, you already know the names.
- G2category pages we watch for workflow and CRM buyer language
- Capterraintent-heavy software roundups that still move mid-market deals
- Product Huntwhere we launch and where we study how adjacent tools pitch
- Dev.toengineering essays on APIs, webhooks, and DX we both read and write
- The New Stackplatform and SaaS architecture coverage for the technical buyer
- Stack Overflow Blogdeveloper-culture writing that shapes how we talk about tools
From people we work with
We replaced a HubSpot–Zendesk–Airtable braid with one object model. Support finally sees the same company the AE sees.
The API is the product. We built a refund console in a day instead of waiting on a services quote.
Onboarding templates were not cute — they mapped to how we actually route inbound. Live in nine days.
Visit or write
Kiln Software Inc. · Austin, Texas. Studio visits by appointment. For press, partnerships, or a first conversation, use the studio desk — this site is the public face of the practice, not a marketplace.