# Gold Star AI > Gold Star AI builds AI Operating Systems: it maps every action in a business, connects the tools and knowledge already there, and builds AI agents to do the work. Source: https://goldstarlabs.ai Machine view: https://goldstarlabs.ai/machine We Build AI Operating Systems. We learn how your business works, connect the tools and knowledge you already have, and build AI agents to do the work. Each one has a clear job and knows when to bring you in. ## At a glance - **Name:** Gold Star AI - **Also written:** Gold Star - **Builds:** AI Operating Systems: connected tools, shared knowledge, and AI agents with one clear job each - **Offerings:** - Components - Industry OS - Custom AI OS - Labs - **Founders:** Thomas Baker & Michael Krebs - **Industries served:** Commercial Real Estate. Deep Tech. Financial Services. Tech Startups. Local SMBs. - **Contact:** michael@goldstarworkflow.com - **Website:** https://goldstarlabs.ai ## What we build - [Components](https://goldstarlabs.ai/components): An AI agent for a specific job, built to work with the tools you already use. - [Industry OS](https://goldstarlabs.ai/industry): An operating system shaped around the workflows and needs of your industry. - [Custom AI OS](https://goldstarlabs.ai/custom): An operating system built around your business, connecting its tools, knowledge and work. - [Labs](https://goldstarlabs.ai/labs): Bring us the problem, and we’ll study it in the lab and build a solution. ## A business, mapped A business is a set of actions. We map each one. What starts it, what it needs, what it can do, who else it talks to, and where it stops. A shared map of the people, systems and actions that make your business work. ### Sales From the first signal to a signed agreement. Every action has a defined job. #### Outbound Find the right opportunities and prepare a relevant approach. #### Cold email Research, draft, review and send are separate actions with separate permissions. #### Prospect research - **Trigger:** A prospect enters the queue. - **Inputs:** Company website, public signals and your ideal customer criteria. - **Work:** Research the company and prepare a brief with sources. - **Boundary:** Cannot contact the prospect or alter their CRM record. - **Output:** A sourced brief for the email-drafting agent. #### Draft an email - **Trigger:** A reviewed prospect brief is ready. - **Inputs:** Research brief, your offer and examples of your writing. - **Work:** Prepare one relevant, personalized introduction. - **Boundary:** Cannot send the message or invent claims. - **Output:** An email draft ready for human review. #### Review & send - **Trigger:** A draft is submitted for review. - **Inputs:** The draft, supporting sources and your sending rules. - **Work:** Present the draft for approval, then send the approved version. - **Boundary:** Sending requires explicit approval and a valid recipient. - **Output:** A sent message and a recorded approval. #### Find buying signals - **Trigger:** The daily signal check begins. - **Inputs:** Your signal criteria and permitted public sources. - **Work:** Find changes that make a prospect worth a closer look. - **Boundary:** Cannot infer unsupported facts or initiate outreach. - **Output:** A shortlist of sourced opportunities. #### Inbound Turn an incoming conversation into a prepared, useful next step. #### Qualify an inquiry - **Trigger:** A new inquiry arrives. - **Inputs:** The inquiry, account history and qualification criteria. - **Work:** Summarize the need and suggest the appropriate next step. - **Boundary:** Cannot promise pricing or accept a project. - **Output:** A qualification brief for your team. #### Prepare a meeting - **Trigger:** A meeting is added to the calendar. - **Inputs:** The invite, CRM history, notes and relevant documents. - **Work:** Prepare context, open questions and previous commitments. - **Boundary:** Cannot edit the meeting or message attendees. - **Output:** A meeting brief available before the call. ### Operations Make the work between teams as deliberate as the work inside them. #### Project delivery Keep commitments visible and prepare repeatable deliverables. #### Prepare a deliverable - **Trigger:** A deliverable request is approved. - **Inputs:** Project context, prior examples and the required format. - **Work:** Produce a first draft in the agreed structure and style. - **Boundary:** Cannot publish, share externally or fabricate missing information. - **Output:** A formatted draft with open questions marked. #### Prepare a handoff - **Trigger:** A project changes stage. - **Inputs:** Scope, decisions, owners and outstanding commitments. - **Work:** Assemble the context the next owner needs. - **Boundary:** Cannot change scope or assign unapproved commitments. - **Output:** A handoff brief for the responsible person. ### Finance Prepare the paperwork and surface exceptions, with approvals where they belong. #### Billing A clear path from completed work to reviewed paperwork. #### Prepare an invoice - **Trigger:** A billable milestone is confirmed. - **Inputs:** Approved scope, billing terms and the completed milestone. - **Work:** Prepare an invoice from the agreed commercial terms. - **Boundary:** Cannot change rates, charge a card or send an unapproved invoice. - **Output:** An invoice draft for approval. ### Relationships Keep context close so the next conversation picks up where the last one left off. #### Follow-through Remember the commitments that matter to your clients. #### Prepare a follow-up - **Trigger:** An agreed follow-up date arrives. - **Inputs:** Conversation history, commitments and relationship context. - **Work:** Draft a relevant check-in in your voice. - **Boundary:** Cannot send automatically or make new commitments. - **Output:** A contextual draft in your review queue. ### Shared foundation The existing tools, connected systems, shared data and knowledge that every part of the business builds on. #### Existing tools & systems We start with the software the business already uses and establish the connections agents need. #### CRM & business records - **Trigger:** Connect your existing systems. - **Inputs:** Your CRM, operational databases and approved access. - **Work:** Make relevant records available through controlled connections. - **Boundary:** Agents only see and change the records their role permits. - **Output:** Connected business records with clear ownership. #### Email & calendars - **Trigger:** Connect your team's communication tools. - **Inputs:** Existing mailboxes, calendars and communication software. - **Work:** Provide the context and channels needed for each approved workflow. - **Boundary:** Reading, drafting and sending are separate permissions. - **Output:** Tools agents can use within their assigned role. #### Shared data & knowledge Build a common picture of the business so agents can work from the same context. #### Documents & knowledge - **Trigger:** Bring the business's knowledge together. - **Inputs:** Documents, procedures, project history and existing files. - **Work:** Organize useful context and make it retrievable with its sources. - **Boundary:** Respect source access; flag missing or conflicting information. - **Output:** A shared knowledge foundation agents can refer to. #### Connected data - **Trigger:** Map the records that belong together. - **Inputs:** Customer, project and operational data across existing tools. - **Work:** Define shared entities, relationships and sources of truth. - **Boundary:** Preserve provenance and surface uncertain matches for review. - **Output:** A consistent understanding of people, work and relationships. #### Access & operating rules Define how the connected system is allowed to operate before giving agents work. #### Permissions & approvals - **Trigger:** Define each role's authority. - **Inputs:** Your existing permissions, business policies and decision owners. - **Work:** Specify what an agent may read, prepare or execute, and when approval is required. - **Boundary:** Actions outside the assigned scope require an authorized person. - **Output:** Explicit boundaries shared across the operating system. #### History & traceability - **Trigger:** Connect actions to their evidence. - **Inputs:** Inputs, tool results, approvals and changes. - **Work:** Record what happened and preserve the context needed to review it. - **Boundary:** Keep records within the business's access and retention rules. - **Output:** An inspectable history of the system's work.