RaymondDeLuca
Menu

Raymond DeLuca · Builder · Operator · Stoin

Your business shouldn't
have to start from scratch.

Conversations, documents, meetings, and decisions should add up to something your team can keep using. We build toward that.

Bring Me a Problem

The missing connection

The request should survive every handoff.

A customer asks for an after-hours installation. Follow that detail through a meeting, solution design, approval, and the final proposal. The difference is who carries the story.

  • Context carried forward
  • Context must be recovered
  • A tool’s own AI feature
01

Your people still connect the story.

Each tool sees its piece of the job. Your team recovers the context at every handoff.

  1. New lead

    This tool has its own AI feature

    Chatbot sees the form

  2. Customer meeting

    Notes captured separately

  3. Team designs solution

    Searches system by system

  4. Approval call

    Decisions need re-entry

  5. Proposal sent

    This tool has its own AI feature

    Reconstructs the brief

One requirement, followed through the work

  1. Customer requestAfter-hours installation
  2. The handoffMissing from the brief
  3. Before sendingReconstruct the decisions
  4. The proposal“After hours?”
Context gets rebuiltInformation scattered across separate systems
  • PMS
  • Orders
  • Email
  • Slack
  • Sheets
  • CRM

The tools hold the pieces. Your people rebuild the story.

02

Connected tools. An assistant that catches up.

Retrieval brings more information together. Details from meetings can still arrive after the decisions.

  1. New lead

    Chatbot logs the request

  2. Customer meeting

    AI catches up afterward

  3. Team designs solution

    AI connects some tools

  4. Approval call

    AI catches up afterward

  5. Proposal sent

    Reassembles the decisions

One requirement, followed through the work

  1. Customer requestAfter-hours installation
  2. After the meetingRetrieve the transcript
  3. After approvalReassemble the decisions
  4. The proposalRebuild the brief
Provider-managed contextConnected information, subject to provider and integration boundaries
  • PMS
  • Orders
  • Email
  • Slack
  • Sheets
  • CRM

Continuity also depends on live participation, useful permissions, and how company knowledge is managed.

03

One synth carries the context and moves the work forward.

Requirements, decisions, and approved actions stay connected across the same customer journey.

  1. New lead

    Finds missing requirements

  2. Customer meeting

    Answers questions in the call

  3. Team designs solution

    Checks constraints; prepares options

  4. Approval call

    Explains changes; captures approval

  5. Proposal sent

    Uses the approved decisions

One requirement, followed through the work

  1. Customer requestAfter-hours installation
  2. Synth asks liveAdd an evening crew?
  3. Human decisionApprove the revised quote
  4. The proposalAfter-hours included
Your company contextRequirements · Decisions · Actions
  • PMS
  • Orders
  • Email
  • Slack
  • Sheets
  • CRM

Same journey. This time you’re riding the dragon.

A synth is a persistent software collaborator. Its job is to help connect the knowledge and work—not take ownership of your decisions.

Follow one customer request →

When meetings lose their context

Put the work in the room.

Actual Utopia Workspaces meeting interface displaying a shared note and its versions, rendered with synthetic QA data

Utopia Workspaces · Real application screen with demo data.

Explore the example →

The problem. You spend half the call finding the right document and bringing everyone up to speed. By the time the context is clear, the meeting is nearly over.

What we changed. We are building a room where people, shared materials, and a business-aware synth can work together. The Workspaces screen shows the shared note and review controls: a place to work on the decision while everyone has the context.

A meeting should move the work forward—not create another round of explanation.

See the principle in practice

When agreement doesn't become action

A decision needs somewhere to go.

Everyone agrees on the next step. A week later, nobody is sure who owns it or which version was approved. The shared note and review controls above give the decision somewhere to live. Our design aim is to carry the next step, its owner, and the reason behind it into the work that follows.

The screen demonstrates shared work and review, not completed automatic follow-up.

Follow-through starts with preserving the commitment.

When information lives in silos

The answer exists.
Make it available.

Public Utopia Homes property page with its Ask Lucy guest assistant open

Utopia Homes · Public guest interface.

Explore the example →

The problem. A customer asks a question your team has answered before. The answer exists—but someone still has to remember where.

What we changed. For Utopia Homes, we connected approved business knowledge to the place guests already ask. Homes Prime brings that knowledge into the website experience, instead of making a person assemble the background for every question.

Customer service should not depend on who happens to remember.

See the principle in practice

When conversations scatter

The chat ends.
The knowledge shouldn't.

Personal Lucy / Continuing the work

Keep the
reasoning.

What did we decide?
Why did it matter?
What should carry forward?

137 past conversationsUsed to build the historical context example · September 28, 2026

Personal Lucy · A historical conversation example.

Explore the example →

The problem. You return to a project weeks later. The decision is somewhere in an old chat, but the reasoning is harder to find. So you explain the whole thing again.

What we changed. We used our earlier conversations to give later work a history to draw on. Personal Lucy turns a body of past discussion into a basis for reusable context: what we explored, what we decided, and why it mattered.

Useful knowledge should not disappear when the chat closes.

See the principle in practice
Raymond DeLuca

Built by an operator

Technology meets
Monday morning.

20+ years in technology. Real estate and hospitality ownership. Harvard AMDP alumnus. These are problems I meet in my own work.

Meet Ray →

Where does your
work lose the thread?

A conversation nobody can find. An answer only one person knows. A meeting that changes nothing. Bring us your version. Through Stoin, we find the break, build a useful connection, and improve it through real use.

Bring Me a Problem →

How we approach the work