PDT
Process Dev Tools is workflow infrastructure for teams building operational software with coding agents. It gives AI-assisted workflows explicit structure: tools, workflows, approvals, durable state, replay, and evaluation.
The goal is not to make automation look magical. The goal is to make generated operational systems understandable, governable, and worth keeping.
What PDT is
PDT helps teams turn recurring business processes into code-owned systems. It is designed for workflows that involve multiple steps, external tools, judgment, review, and operational risk.
Why the framework matters
Coding agents can generate a lot of software. The useful question is whether that software lands in a structure that engineering can review and maintain. PDT is meant to provide that structure.
What we mean by it
Workflow engineering is the practice of building operational software that coordinates systems, humans, policy, and AI. It sits somewhere between ops design and software engineering.
Who it is for
The clearest fit is teams in operations functions such as RevOps, SalesOps, MarketingOps, SupportOps, and FinanceOps, along with the engineers who need to own the systems those teams rely on.
How PDT fits
PDT is intended to be the framework layer for that work: a way to build operational systems through code generation without ending up with brittle workflow glue.
Implementation and advisory
We work with teams that want to design, validate, and ship workflow-engineered systems on the PDT stack. That can include operational workflow design, framework adoption, or building the first capability with your team.
Examples of good fits
Dispute handling, approval-heavy reviews, intake and routing, internal casework, operational audits, process mapping, and other workflows where manual work is expensive but full automation would still be irresponsible.