- Context scattered across documents and inboxes
- Outputs separated from source material
- No ownership of review, approvals, or next steps
- No memory of workflow state after the prompt
Labs
Labs are where product bets meet industry constraints.
Each lab starts with a workflow wedge: repeated documents, expensive handoffs, expert review, and a clear path to a vertical product. This is where we turn the broad Pragma ambition into specific products people actually use.
Processual
Portuguese legal teams work through dense process documents, scattered context, repeated drafting, and high-cost review cycles. Processual turns that operating layer into source-grounded context, lawyer-reviewed outputs, and controlled next steps.
Visit Processual → Active Lab 02EduNexo
Portuguese teachers need a clearer way to organize learning evidence and reach evaluation decisions without rebuilding the record at the end of the period.
Visit EduNexo →Workflow diagnosis
Your team does not need another chatbot. It needs the work to move.
Most AI pitches assume the hard part is generating an answer. In professional work, the hard part is everything around the answer: finding the source, preserving context, knowing who reviewed it, and moving the next task forward without breaking trust.
- Structured context from the actual source documents
- Drafts and decisions tied back to evidence
- Human review designed into the workflow
- State, permissions, quality checks, and iteration loops
The Pragma loop
Find the wedge. Build the product. Prove adoption.
We are not trying to sell generic AI transformation. We look for one expensive, repeated workflow where a narrow product can create a visible before-and-after for a specific professional team.
Map the workflow pain
We start with the work people already do: documents received, facts checked, drafts produced, reviews requested, and deadlines tracked.
Build around the operator
The first version is narrow on purpose: one user, one workflow, source-grounded outputs, and a review loop that matches how risk is handled today.
Keep only what earns repeat use
The metric is not demo applause. The metric is whether real users return to the workflow because it saves effort without lowering professional control.
Fit test
There may be a product hiding in the workflow when the same signals keep showing up.
The best labs are not vague markets. They are workflows with enough pain, repetition, risk, and document gravity that a product can become part of daily work.
Lab criteria
What makes a workflow worth a lab?
Repeated pain
The work happens often enough that a product can become habit.
Document gravity
Important context sits in files, messages, templates, and records.
Expert review
The output carries enough risk that judgment and provenance matter.
Product wedge
One narrow workflow can prove value before the system expands.