Matt McGreal
I design and build
Intelligent Operating Systems
Systems that preserve context, clarify decisions,
coordinate action, and move work forward.
Discovery • Design • Intelligent Systems
Work
Arc
Clinical Operations Intelligence
Arc helps clinical education teams turn fragmented scheduling requests and student information into clear, prioritized human decisions while preserving the context, communication, and operational history needed to keep assignments moving.
Who
Clinical education teams responsible for student rotations, clinical-site assignments, schedule changes, constraints, and communication with students and site coordinators. Arc was shaped around the operator who must review incoming changes in context and decide what happens next.
The Problem
Post-distribution schedule changes often begin as Google Form submissions, but making a decision requires much more than reading the request. The operator may need the student, current assignment, site availability, specialty requirements, time-off constraints, previous placements, calendar conflicts, and downstream effects. The information exists, but it is fragmented across schedules, records, requests, and people.
The Thinking
The problem wasn’t simply capturing requests. It was reconstructing enough trusted context to make the right decision. Rather than replace the full scheduling ecosystem, Arc narrowed the first product around one high-value workflow: structure the request, evaluate impact and constraints, surface what requires attention, support the human decision, and record what happened.
The System
Arc organizes the workflow around four core capabilities.
- Automated Intake / Capture — Existing Google Forms remain the front door. Incoming requests become structured Arc records.
- Operational View — A prioritized Attention Queue surfaces requests needing judgment with evidence, current and proposed assignment, risk, recommended action, and decision controls.
- Assignment Timeline — A visual view of students, clinical sites, and assignment periods makes changes, availability, and potential conflicts easier to understand.
- Student Record — Assignments, requests, decisions, correspondence, constraints, credentials, and execution history remain connected in one longitudinal record.
How It Works
- Request received A post-distribution scheduling change enters through Google Forms.
- Context assembled Arc connects the request to the relevant student, site, assignment, schedule, and constraints.
- Risk evaluated Coverage, conflicts, specialty requirements, time-off considerations, and downstream effects are checked.
- Attention surfaced Requests needing judgment rise into the operator’s Attention Queue with the evidence needed to act.
- Human decision The operator approves, denies, escalates, or requests clarification. Human judgment remains in control.
- Loop closed Required schedule updates, communication, and decision history are captured as part of the operational record.
Tools / System Components
My Role
Current State
Arc has moved from broad ecosystem discovery to a focused working model centered on the post-distribution change process. The core workflow is validated in concept: requests commonly enter through Google Forms, schedule impact and downstream consequences matter, the operator reviews and decides, and stakeholders must be informed afterward.
Remaining validation centers on exact update behavior, notification timing, and the minimum on-screen context needed before a decision.
Outcome goal: Fewer context switches. Clearer risk. Better-supported decisions. A durable record of what changed, why, and what happened next.
Work
Nexus
Real Estate Intelligence
Nexus helps real estate professionals focus on the relationships and decisions that change outcomes by organizing attention, client context, and next actions in one calm, trusted operating layer.
Who
Independent real estate professionals and small teams managing buyers, sellers, and transactions across listings, contracts, inspections, lenders, and closing. Nexus was shaped with a working real estate professional to match how the work actually moves.
The Problem
Real estate work lives in email threads, paper files, site logs, calendars, and memory. Deadlines slip, follow-ups fall through the cracks, and vital context is scattered. The cost is stress, rework, and deals that become unnecessarily complicated.
The Thinking
The most important moments are the ones where the agent’s judgment or action can change the outcome. Nexus doesn’t try to be everything. It assembles the right context, surfaces what needs attention, and gives the agent clear ways to act, then records what happened. Simple, focused, and quiet when it is working.
The System
Nexus organizes the daily flow of real estate work around five core capabilities.
- Attention Cards — Surface what needs action now: Due Today, Overdue, Waiting, Coming Next, and At Risk.
- Ask + Composer — Retrieve the right client context quickly and compose useful correspondence without leaving the workspace.
- Add & Capture — Structured intake for leads and transactions, with progressive fields as relationships deepen.
- Client Workspace — Key details, notes, dates, documents, history, and follow-ups live together.
- Action & Follow-Through — Create deadlines and follow-ups, complete them, and move the item to its next state automatically.
How It Works
- Lead or item captured A new lead, client, deadline, or transaction enters through the Add flow.
- Context assembled Client details, dates, notes, documents, and communication references connect to the record.
- Attention surfaced Nexus evaluates dates, status, and dependencies and places the item in the right Attention state.
- Agent takes action Ask and Composer help retrieve context or prepare the right correspondence with the relevant client information already in view.
- Action completed Deadlines and follow-ups are marked complete with timestamp and history.
- State updated The item leaves the queue or advances to its next state without extra tracking work.
Tools / System Components
My Role
Current State
Nexus’s core experience is being built around the complete operational thread: capturing leads and client records, surfacing what needs attention, loading the right context, supporting the action, and recording completion.
The focused MVP keeps deeper email, calendar, and intelligence layers secondary until the core workflow is reliable and useful in real transaction work.
Outcome goal: Fewer things slip. Less rework. Clearer next actions. More time for clients and outcomes, not admin and chasing.
Approach
About
My work happens at the intersection of business, technology and humans.
I’m Matt McGreal. I design and build intelligent operating systems that turn fragmented workflows, decisions, and information into something people can actually use.
My approach starts with understanding how the work really happens, then shaping the simplest system that can preserve context, support judgment, and move the operation forward.
