Products that earn their complexity.
Products, platforms, internal tools, and the interfaces around them.
Dazed Unicorn
Clarity for strange systems.
We build software, shape how teams work, and turn messy projects into something usable, durable, and sharp.
For work that's too unusual for templates and too real for vibes.
Workbench / Work
A small shop. Software, systems, and sharper ideas.
We turn messy problems into tools, language, and structures that hold up.
Structure for work that keeps slipping sideways.
Operations, roles, processes, automations, and the decisions behind them.
Language with enough precision to be useful.
Naming, positioning, and the words that let work travel.
Workbench / Projects
A few things we've built.
The best work isn't always the loudest. These show judgment under constraint.
RoleRivr
Operational SaaS system
- What A workforce platform: tenants, teams, roles, shifts, subscriptions, and AI-assisted scheduling.
- Key decisions
- Tenant-first architecture with RLS-backed data isolation
- Explicit membership and role model
- Stripe-connected subscription state
- Shift scheduling around teams, locations, and availability
Outcome A SaaS foundation with tenancy, access, scheduling, and billing modeled directly.
TypeBlossom
Learning behavior product
- What A typing platform built around practice, feedback, and measurable improvement.
- Key decisions
- Design for practice, not one-time consumption
- Make progress visible
- Treat motivation and friction as architecture
Outcome Proof the work reaches past operations software—into behavior, learning, and skill-building.
Workbench / Systems
Bring the thing that keeps changing shape.
Some problems don't need more enthusiasm. They need better edges.
We turn messy products and half-formed ideas into structures that can be named, tested, and handed off.
Common repairs
-
Repair 01
Product direction
Clarify what the product is, who it's for, and what ships first.
-
Repair 02
Operational systems
Turn scattered roles, repeated decisions, and hidden dependencies into working structure.
-
Repair 03
Workflow design
Map how work actually moves and build a flow that doesn't depend on memory or one heroic person.
-
Repair 04
Automation planning
Separate judgment from repeatable tasks. Decide what to automate, assist, or leave manual.
-
Repair 05
Naming and positioning
Give unclear work language strong enough to travel: names, claims, and categories.
-
Repair 06
Execution support
Move from fog to shipped artifact: prototype, repo, page, tool, or decision doc.
How it looks in practice
Tenant Migration
Private infrastructure case- What A live schema migration moving a product from org-scoped assumptions to tenant-first multi-tenancy—without a rewrite.
- Key decisions
- Backward-compatible transition supporting both org and tenant IDs during the move
- Layered tenant membership, roles, and locations
- Indexed RLS policies for isolation and performance
- Idempotent SQL repairs with verification at each step
Outcome Cleaner ownership, safer access, stronger indexes, and a clear path off the legacy structure.
Workflow Engine
Internal operations system- What An internal system turning manual steps into explicit decision paths and reusable flows.
- Key decisions
- Convert repeatable judgment into explicit flows
- Separate human decisions from automatable steps
- Fewer dropped threads, faster setup, clearer next actions
Outcome Less noise, faster shipping, clean line between public surface and private machinery.
Product Direction
Scope, positioning, and execution- What Turning a broad idea into a ship-worthy shape: what it is, who it's for, what ships first.
- Key decisions
- Define the smallest credible public surface
- Proof-heavy artifacts over feature lists
- Ship a version that exists, not one that might
Outcome Sharper positioning, cleaner scope, a story that holds across software, consulting, and creative work.
Workbench / Method
Find the real pressure. Make the shape clearer. Build only what holds.
We start where friction lives—the part of a system where confusion, repetition, or risk keeps showing up.
-
Observe the machine
Where does work stall, repeat, or live in someone's head?
-
Name the pressure
Find the real constraint before solving the wrong one.
-
Choose the smallest strong shape
The minimum structure that can actually hold: boundary, workflow, model, script, migration.
-
Build the holding piece
Ship what reduces risk or creates the next foothold. Not everything becomes a platform.
-
Leave the system easier to use
Less fog. Cleaner paths. A system that's easier to maintain.
No theater. No generic transformation language. No pretending every problem is solved by software.
Workbench / Contact
Send a signal.
For software, consulting, systems design, product direction, or creative work that needs a sharper shape.
A few useful things to share
- What are you trying to make, fix, clarify, or ship?
- What is stuck?
- What does success look like?
Workbench / About the shop
Behind the work.
Dazed Unicorn is a small company led by Ashley Harveco.
The work moves across software, systems, product direction, operations, positioning, and creative infrastructure. The shape changes. The standard doesn't: find the real pressure, make the shape clearer, and build what holds.