Dryvn AI · Adaptive business systems
The AI operating system for the way your business works.
Dryvn is developing an operating system that connects business records, workflows and authorized actions around the way an organization works. Our adaptive archetype approach starts with a shared foundation, then configures the capabilities, language and rules for the operation.
Text and voice provide a natural way in. The dashboard provides visibility, configuration and control.
06 — Fit and development
Start with the way work moves through your business.
Dryvn’s foundation comes from operational experience running complex residential development operations. That grounding is why the architecture starts with the job and project pattern; it is not a limit on the kinds of business the architecture is intended to serve.
Most mature starting point
Job and project work
A request becomes scoped work with an estimate, scheduled work, documentation and billing. Example: a renovation request is matched to the customer, opened as a job, estimated, followed up until answered, scheduled, documented and invoiced, with the owner asked only where a decision is needed.
Development and evaluation areas
Further operating patterns
Appointment-based businesses, property and asset management, sales pipelines and other patterns are being developed on the same foundation. They are described as direction until the capabilities and workflows for an implementation are verified.
02 — Product evidence
See the working product.
See how an instruction is handled in Dryvn, and how the operating record remains visible in the dashboard.
Both are unedited screen recordings of the Dryvn product.
Product recording
Conversation and action
A text conversation with Dryvn in which an instruction is understood and handled against the business record.
Product recording
The operating record
The dashboard where the record, the state of the work and the controls remain visible.
03 — Architecture
One foundation. Configured for the operation.
Businesses in different industries can share the same operating pattern. A project still needs a record, a responsible person, an agreed next step and a way to establish completion. Dryvn’s archetype approach starts with that pattern and configures the surrounding experience.
In one sentence
DAAOA, Dryvn Adaptive Archetype Operating Architecture, is Dryvn’s approach to configuring an AI operating system around the way a business works: a shared foundation, then the terminology, workflows, rules and permissions appropriate to the organization.
- 01Business contextThe relevant customers, work, documents and history. Dryvn holds some of these records; others stay in the systems a business already relies on.
- 02Configured capabilitiesThe functions, terminology and workflows the organization needs, enabled from a shared set rather than rebuilt per industry.
- 03Operating controlsPermissions, approvals and responsibility for exceptions, set for the implementation rather than assumed.
Dryvn’s job and project operating model is its most mature starting point. Broader archetype support and further adaptation are development areas; availability depends on the capabilities and workflows verified for each implementation.
04 — Connected operations
Build on the systems that already work.
Some records belong in Dryvn. Others belong in the software a business already relies on. The implementation determines where each record belongs and which supported actions Dryvn can perform across those systems.
Product integrations are listed with their current status. A scoped Dryvn Ops implementation is a separate engagement built around an organization’s own systems.
05 — Workflow and human judgment
Give each step a record, an owner and a next action.
A useful operating system needs more than a generated response. It needs to know which record is involved, what action is permitted, how a result is checked and who takes responsibility when the work needs attention.
Which checks and approvals apply is set for each implementation.
Text version of this diagram
- Customer request arrives (start) → go to Identify the record
- Identify the record (step; customer, job, history) → go to Permitted without approval?
- Permitted without approval? (decision) → yes: go to Carry out the step; no: go to Ask the responsible person
- Carry out the step (step; message, booking, document) → go to Result checked?
- Ask the responsible person (waiting state; approval or decision) → approved: go to Carry out the step; declined or no answer: go to Needs review
- Result checked? (decision) → yes: go to Resolved and recorded; no, or unexpected reply: go to Needs review
- Resolved and recorded (end)
- Needs review (escalation to a person; named owner) → person decides, work resumes: go to Identify the record
Illustrative workflow.
07 — Learning library
Understand the systems behind the work.
Explainer
What is an AI system, a workflow and a loop?Learn the difference between a system, a workflow, an automation, an agent and a feedback loop using two everyday business examples, and map one of your own on a worksheet.
Worksheet
What should AI be allowed to do without asking?Decide, action by action, what an AI assistant or automation may do on its own, what it may do inside an approved scope, and what always waits for a person.
Explainer
Knowledge graphs and workflow graphs, explained for business ownersTell knowledge graphs from workflow graphs, see each drawn with a fictional example, and decide which relationships and decisions your business should record.
Explainer
How AI uses your documents: search, context and retrievalUnderstand what actually happens when an assistant answers from your company documents, why that is not the same as training, and what to check before you trust the answer.
From the blog: An answer is not an outcome: what has to be true before AI can finish work for you
08 — Questions
Questions about using Dryvn
Often that is the right starting point. Review the supported connections and decide where each record should remain authoritative before anything is automated.
A connected assistant may already meet the need. Compare the actions, records, scheduling, permissions and exception handling the work requires against what your actual configuration supports.
Permissions and approval requirements are scoped to the implementation. Money, commitments and anything irreversible are designed as approval steps; which controls apply to a given workflow is reviewed before relying on unattended execution.
Start with one documented workflow, its owners, the systems it touches and the result you need. That is what a fit conversation reviews.
Explore what Dryvn could support in your operation.
Bring one workflow, the systems it touches and the outcome you need. We will review the fit and the capabilities currently available.