The Studio Experience

Replacing a manual configuration nightmare with a visual, intuitive workflow builder.

Timeline 2.5 Years
Team 2 PMs, 5 Engineers
The Studio Experience

The Impact

Studio is the configuration environment where business admins define the data, workflows, and rules for their applications.

50% Faster Implementation
92 Enterprise Customers

Speed and Flexibility

The Challenge

Disconnected Task Lists

In previous solutions, configuring a business process was restricted to linear checklists. While this worked for simple to-do lists, it failed for actual case management.

The Mismatch: A case isn’t a linear list; it’s a lifecycle. It moves through stages, branches based on data, and triggers automated side-effects.

The Friction: User research revealed that users struggled to understand this lifecycle when looking at a simple grid. They had to mentally track dependencies. One wrong number in a “Precedents” column could break the flow, and there was no way to “see” the error until runtime.

Legacy Interface showing complex grid

The legacy ‘Task Grid’ interface. Notice the cognitive load of tracking precedents by ID number.

The Solution

01

The Hybrid Workflow Builder

Speed + Validation

To solve the visualization problem without sacrificing data entry speed, the solution utilizes a three-pane configuration interface that bridges the gap between a spreadsheet and a flowchart:

  • Input (Left & Middle): A list-based input allows for rapid data entry of task details.
  • Logic (Middle): A dedicated configuration area for defining milestones, SLAs, and—crucially—dependents.
  • Validation (Right): As the user configures logic, the right pane updates in real-time to visualize the workflow graph.

The UX Win: Users could work quickly in a list format, but the instant visualization allowed them to verify complex paths immediately.

Configured workflow template
A fully configured workflow template.
Workflow configuration in progress
Defining logic within a workflow step.
02

Systemic Automation

Hierarchy & Inheritance

User feedback highlighted that automation needs varied based on scope—some rules are global, while others are hyper-specific.

The Strategy: A hierarchical automation engine supports cascading logic: Global Level (All Cases) → Category Level (Permits) → Case Type Level (Plumbing Permit).

Execution Logic: To handle conflicts, the system executes from the highest level down to the lowest level. This ensures global compliance is respected while allowing specific case types to define “exceptions” that take precedence.

Automation rules at different hierarchies
The high-level view of automated rules across the system hierarchy.
Configuring an automation rule action
Configuring a specific action within an automation rule.
03

Integrated Data & Form Designer

No-Code Modeling

A workflow requires data inputs. Previously, adding a form field required an IT ticket to modify the database. The no-code form builder puts this power in the hands of the business admin.

  • Implicit Data Modeling: When a user adds a field to a form, the system automatically creates the backend data structure.
  • AI Acceleration: AI integration speeds up data creation. Users can prompt the system (e.g., “Create a dropdown for US States”), and the AI generates the data type and all options automatically.
  • Accessibility by Default: All components automatically meet WCAG 2.1 AA standards.
Configured forms for a Case Type
The Case Type view showing configured forms.
Form creation interface
The form creation interface.
AI-assisted data capture
AI-assisted data field capture.
04

Built for Extensibility

The Platform Mindset

To support diverse customer needs, the Studio design is agnostic and extensible. The architecture supports custom task types, email templates, and automation rules. Customers can plug in their own specialized logic (like a “Fraud Check” rule) and have it render natively within the Studio UI alongside standard features.

Centralized Branding: A unified location was designed where all colors and styling are defined. By changing a single set of values, customers can instantly rebrand the entire system—from the Studio configuration environment to the Workspace front-end—ensuring every deployed application matches their corporate identity without manual styling updates.