{"version":"1.0.0","generated":"2026-06-09T16:31:47.414Z","source":"https://y-infra.com/capabilities","description":"YInfra Business OS capabilities — each module described with verticals, integrations, replacement targets, and an LLM-readable summary.","capabilities":[{"id":"crm","name":"CRM & Lead Management","llmSummary":"Full CRM with lead scoring, pipeline stages, deduplication, notes, tasks, and disposition tracking -- replacing spreadsheets and generic CRM tools.","description":"YInfra's CRM is the operational center of the business operating layer. Every contact -- whether they arrived through a web form, a missed call, a DM, or a manual import -- lands in one unified record with a clear stage, a lead score, disposition tags, and a timestamped history of every interaction. The pipeline is not a spreadsheet with columns; it is a living workflow where leads move from intake through qualification, active follow-up, proposal, and closed status, with automated next-step prompts at each gate.\n\nLead scoring runs on a configurable model that weights source, response behavior, engagement recency, and business-specific signals. A med spa that values referred clients over cold web leads can weight referral source accordingly. A private lender that cares about deal size can configure scoring around that signal.\n\nDeduplication catches duplicate contacts on create and merge, so the pipeline stays clean without manual audits. Notes are rich-text and time-stamped, visible to the full team. Tasks -- calls to make, follow-ups to send, proposals to draft -- sit directly on the contact record, never in a separate tool. The dispositions system lets owners codify exactly what \"dead lead,\" \"nurture,\" \"hot,\" and \"closed\" mean for their business, so pipeline stage means the same thing to every staff member.\n\nFor local businesses, this replaces a spreadsheet, a generic CRM subscription, and the staff memory that currently holds the customer journey together. For private lenders, the same system becomes a deal pipeline with borrower, broker, and investor relationships tracked through every stage from inquiry to funded.","status":"live","verticals":["Med spas and clinics","Home services","Local SMBs","Private lenders","Content creators"],"integrations":["Calendar / scheduling","Payment processor","React Email","Automation layer"],"replaces":["GoHighLevel CRM","HubSpot CRM","Salesforce Essentials","Spreadsheets","Pipedrive"],"url":"https://y-infra.com/capabilities/crm"},{"id":"pipeline","name":"Pipeline Tracker","llmSummary":"Stage-enforced pipeline tracker with Kanban/list views, filters, analytics feed, and relationship mapping for deals, clients, and projects.","description":"The pipeline tracker gives owners and operators a real-time view of where every deal, client, or active engagement sits in the business cycle. Unlike a CRM that merely stores contacts, the pipeline tracker enforces stage logic: a contact cannot move to Proposal Sent without a consultation completed, and cannot move to Active Contract without a proposal signed. This keeps the pipeline an honest view of business health, not a wishful forecast.\n\nKanban and list views are both supported, so operators who think visually can drag cards between stages while team members who prefer lists can work in tabular form. Pipeline filters let an owner answer questions like how many leads are sitting in follow-up for more than 7 days or which deals came from the referral program this quarter without exporting to a spreadsheet.\n\nFor private lenders, the pipeline tracks deal stage from initial inquiry through underwriting handoff, commitment letter, closing, and funded -- with borrower, broker, and investor records linked as related entities on each deal. Relationship graphs show who introduced a deal, who is co-investing, and what the broker's historical close rate is.\n\nThe pipeline feeds owner analytics directly, so the dashboard KPIs -- leads in, booked work, conversion rate, average deal cycle -- are computed from live stage data, not manually entered. No data entry happens twice.","status":"live","verticals":["Private lenders","Med spas and clinics","Home services","Local SMBs"],"integrations":["CRM","Owner Analytics","Automation layer"],"replaces":["Monday.com","Trello","Notion deal trackers","Salesforce pipeline"],"url":"https://y-infra.com/capabilities/pipeline"},{"id":"openclaw","name":"OpenClaw -- AI Co-Pilot","llmSummary":"In-console AI assistant with tool access to live CRM data -- drafts emails, triages leads, surfaces history, and answers business questions in natural language.","description":"OpenClaw is the AI assistant built into the YInfra operator console. It is not a chatbot bolted on the side of the product -- it is an agent with hands, able to read and act on the live data inside the console, draft emails, triage leads, surface relevant contact history, and answer questions about the business without leaving the workflow.\n\nThe model is scoped deliberately. OpenClaw assists with drafting and triage; it does not make decisions autonomously. Every drafted email, every lead disposition suggestion, and every action proposal sits in a human review step before it executes. This is the core design principle: AI placed inside a stable workflow with clear staff ownership and review boundaries, not bolted on as a demo that sits unused.\n\nPractical uses include: drafting a follow-up email from a lead record with one click, summarizing the last five interactions with a client before a call, flagging leads that have gone quiet beyond a configurable threshold, and searching across the full contact and note history in natural language. For private lenders, OpenClaw can surface all deals in a given stage, identify borrowers whose last touch was over a week ago, and draft outreach.\n\nThe tool library is extensible -- new tools can be registered to give OpenClaw access to additional capabilities as the console grows. The agent loop runs in the browser console with streaming responses, keeping latency low and the experience conversational.","status":"live","verticals":["All verticals"],"integrations":["CRM","Pipeline","React Email","Supabase"],"replaces":["ChatGPT sidebar","Notion AI","HubSpot AI assistant"],"url":"https://y-infra.com/capabilities/openclaw"},{"id":"security-ai","name":"Security AI -- Computer Vision","llmSummary":"Operationally scoped computer vision -- room utilization tracking for med spas, retail queue monitoring, and premises security with output as structured console data.","description":"YInfra's security AI capability applies computer vision to the physical spaces and operational workflows of client businesses. The system ingests camera feeds and runs trained models that are scoped to the specific workflow the business cares about -- not generic surveillance, but operationally relevant monitoring tuned to each deployment.\n\nFor a med spa, the relevant model might track room utilization: which treatment rooms are occupied, how long each session runs, and when rooms are idle longer than the target turnaround. This gives the operator visibility into utilization rates that currently require manual tracking or are simply unknown. For a retail business, queue monitoring can trigger alerts when the checkout line exceeds a threshold, allowing staff to open additional lanes before the friction reaches the customer. For premises security, the model distinguishes routine activity from access anomalies without requiring a human watching a monitor all day.\n\nModels are trained on the specific visual patterns of the client's space, not on generic training sets that misfire constantly in unfamiliar environments. The output is not raw video or a stream of alerts -- it is operationally structured data: room-state changes, utilization summaries, and threshold events, surfaced in the operator console as analytics and real-time flags.\n\nData residency and privacy posture are scoped explicitly for each deployment. No consumer facial recognition is used. The capability is designed for operational efficiency and premises safety, not surveillance.","status":"roadmap","verticals":["Med spas and clinics","Retail businesses","Home services (premises)"],"integrations":["Supabase","Owner Analytics"],"replaces":["Generic CCTV with no analytics","Manual room tracking","Third-party queue management"],"url":"https://y-infra.com/capabilities/security-ai"},{"id":"graph-db","name":"Graph Database Layer","llmSummary":"Relationship intelligence layer -- models client treatment history, referral networks, broker trees, and investor relationships with graph traversal queries.","description":"The graph database layer is YInfra's relationship intelligence capability -- a layer on top of the relational data that learns and surfaces the patterns of connection that matter most to each vertical.\n\nFor a med spa, the graph models the relationship between clients and their treatment history, referral source, and referring client. Over time, it can surface which treatments drive the highest re-booking rates, which clients have referred the most new business, and what the typical path from first visit to high-value client looks like. This is not a report you run once -- it is a living map of the business's relational dynamics.\n\nFor MCA (merchant cash advance) and private lending, the graph models broker trees: which brokers introduce which borrowers, what each broker's historical close rate and deal quality look like, and which funders have participated in similar deals. The broker-borrower-investor triangle is a graph problem, not a table problem -- standard relational queries cannot traverse it efficiently. The graph layer makes a query like who else has this broker worked with an instant answer rather than a manual investigation.\n\nFor referral-based local businesses, the graph tracks referral networks: who referred whom, what the downstream value of each referring client is, and which marketing channels produce the highest-quality referral relationships.\n\nThe graph layer is built on Supabase's relational foundation with graph traversal patterns layered on top -- no separate graph database infrastructure is required for deployment.","status":"roadmap","verticals":["Med spas and clinics","Private lenders","MCA operators","Referral-driven local businesses"],"integrations":["Supabase","CRM","Pipeline","Owner Analytics"],"replaces":["Manual relationship tracking","Neo4j standalone","Spreadsheet broker trees"],"url":"https://y-infra.com/capabilities/graph-db"},{"id":"branded-email","name":"Branded Email","llmSummary":"In-console branded email composition and sending built on React Email -- mail-client-safe HTML in the client's brand, logged to the CRM, connected to any mailbox.","description":"YInfra's branded email capability lets operators compose and send customer-facing email from inside the console, wrapped in mail-client-safe HTML that carries the client's brand -- their logo, colors, typography, and tone -- without requiring a separate email marketing platform or design tool.\n\nBuilt on React Email, the composition experience is live and visual: operators draft in a rich-text interface, select from branded templates, and preview the email rendered as it will appear in Gmail, Outlook, and Apple Mail before sending. No code is required to compose a branded transactional email or a client follow-up.\n\nThe system connects to any outbound mailbox -- Google Workspace, Microsoft 365, or a dedicated transactional sending domain. Deliverability is configured at setup: SPF, DKIM, and DMARC records are established as part of the onboarding so emails arrive in inboxes, not spam folders.\n\nFor a med spa, branded email handles appointment confirmations, treatment follow-ups, and re-engagement sequences, all carrying the spa's visual identity rather than a generic platform template. For a private lender, it handles deal status updates, rate sheet delivery, and investor communications. For content creators, it delivers newsletter issues and brand deal confirmations with the creator's established visual brand.\n\nEmail activity is logged in the CRM -- every email sent to a contact appears in their interaction history, so the full conversation thread is visible in one place without toggling between a CRM and an email client.","status":"connect","verticals":["Med spas and clinics","Private lenders","Local SMBs","Content creators"],"integrations":["React Email","Google Workspace","Microsoft 365","CRM"],"replaces":["Mailchimp","Klaviyo","HubSpot email","GoHighLevel email"],"url":"https://y-infra.com/capabilities/branded-email"},{"id":"booking","name":"Calendar & Booking","llmSummary":"Calendar and scheduling integrated with the CRM -- public booking pages, team calendars, open-source or Google/Outlook sync, and automated reminders with CRM pipeline updates.","description":"YInfra's booking capability integrates a full calendar and scheduling layer into the operator console, connecting inbound booking requests to the CRM pipeline without any manual data entry between systems.\n\nIntegrating with your calendar and scheduling system (open-source options, or Google/Outlook), the booking system supports both internal team calendars and public-facing booking pages. A med spa can publish a branded booking page for consultations and treatment appointments; a home services company can expose booking for estimates and service windows; a private lender can publish a calendar link for deal intake calls. Each booking automatically creates or updates a CRM record, sets the appropriate pipeline stage, and schedules any configured follow-up tasks.\n\nCalendar connectivity supports Google Calendar, Microsoft Outlook, and CalDAV-compatible systems, so operators and team members can use the tools they already depend on while bookings flow into the YInfra console. Double-booking prevention is handled automatically across connected calendars.\n\nRound-robin and team booking are supported, so businesses with multiple service providers can route bookings to the appropriate staff member based on availability, service type, or territory. Buffer times, advance booking windows, and cancellation policies are all configurable.\n\nAutomated reminders -- email and SMS -- can be triggered at configurable intervals before appointments, reducing no-shows without requiring staff to manually send confirmation messages. Post-appointment follow-ups flow into the CRM as tasks, keeping the customer journey intact through the entire engagement.","status":"connect","verticals":["Med spas and clinics","Home services","Local SMBs","Private lenders"],"integrations":["Calendar / scheduling","Google Calendar","Microsoft Outlook","CRM","Automation layer"],"replaces":["Acuity Scheduling","Calendly","Square Appointments","GoHighLevel calendar"],"url":"https://y-infra.com/capabilities/booking"},{"id":"finances","name":"Finances & Payments","llmSummary":"Payment-processor-connected finance layer -- in-console invoicing, payment collection, revenue dashboard, and deal-level tracking with CRM and pipeline integration.","description":"YInfra's finance capability brings payments, invoicing, and a high-level financial view into the operator console through integration with your payment processor, replacing the pattern where billing happens in one tool, the CRM lives in another, and the owner has no unified view of what the business is actually collecting.\n\nInvoice creation happens in-console: the operator selects a client from the CRM, specifies line items and amounts, and sends a processor-backed invoice in the client's branded format. Payment links can be embedded in booking confirmation emails, sent as standalone URLs, or processed at a physical point of interaction using your processor's payment collection flows.\n\nThe financial dashboard shows collected revenue, outstanding invoices, payment aging, and refund history -- all drawing from the processor's live data without requiring a separate accounting system for operational visibility. For an owner who currently answers how much did we collect this month by logging into their payment processor, running a CSV export, and manually totaling it, this view provides the same answer in one glance inside the console they already use every day.\n\nFor private lenders, the finance view can be scoped to track deal-level revenue: origination fees collected per deal, investor distributions, and portfolio-level cash flow, connected to the deal pipeline so financial performance and deal activity live in one view.\n\nMarketplace and multi-tenant billing patterns are supported through the connected payment processor, and webhook automation via the automation layer can trigger CRM updates -- marking a contract active when a deposit clears, or moving a deal stage when payment is confirmed.","status":"connect","verticals":["Med spas and clinics","Home services","Local SMBs","Private lenders","Content creators"],"integrations":["Payment processor","CRM","Automation layer","React Email"],"replaces":["QuickBooks Online","FreshBooks","Wave","Square billing","GoHighLevel payments"],"url":"https://y-infra.com/capabilities/finances"},{"id":"marketing-social","name":"Marketing & Social Media","llmSummary":"Social scheduling, multi-platform post composition, and ad tracking through social publishing tooling -- owned and self-hostable, integrated with the CRM for closed-loop marketing visibility.","description":"YInfra's marketing capability brings social media scheduling, post composition, and ad performance tracking into the operator console integrated with social publishing tooling, or the channels you already use -- so content publishing and CRM activity live in one owned system rather than being split across separate subscriptions.\n\nPost composition supports multi-platform scheduling: a single piece of content can be adapted for Instagram, Facebook, LinkedIn, and Google Business Profile and scheduled from one interface. The visual calendar shows the full publishing schedule, making it easy for a business owner or marketing manager to maintain a consistent posting cadence without logging into multiple platform dashboards.\n\nAI-assisted caption drafting is available through the OpenClaw co-pilot, which can generate platform-appropriate copy from a brief typed into the console. Draft output is always reviewed before scheduling -- the AI assists, it does not autonomously publish.\n\nFor local businesses running Google Ads or Meta Ads alongside organic content, ad performance data can be surfaced alongside CRM pipeline data, giving the owner a single view connecting ad spend to inbound leads to booked work. This closes the loop between marketing investment and business outcome that is currently invisible when ads live in one platform and the CRM lives in another.\n\nThe social publishing tooling can be self-hosted as part of the YInfra infrastructure layer, meaning the client's content schedule and audience data are not locked inside a third-party SaaS platform that charges per post or per seat.","status":"roadmap","verticals":["Local SMBs","Med spas and clinics","Content creators","Home services"],"integrations":["Social publishing","CRM","OpenClaw","Automation layer"],"replaces":["Buffer","Hootsuite","Later","Sprout Social","GoHighLevel social planner"],"url":"https://y-infra.com/capabilities/marketing-social"},{"id":"admin-rbac-payroll","name":"Admin, RBAC & Payroll","llmSummary":"Role-based access control, team management, and payroll module -- scoped console views per role, user invitation, time tracking, and audit logging.","description":"YInfra's admin module gives business owners full control over who can see and do what inside the console, with role-based access control (RBAC) that maps to the actual hierarchy of most local businesses: owner, manager, and staff member, each with a tailored view that shows only the surfaces relevant to their role.\n\nAn owner sees the full console -- pipeline, analytics, finances, team management, and settings. A front-desk staff member sees the booking calendar, the intake queue, and the CRM contacts they are authorized to manage. A billing administrator sees finances and invoices but not the lead pipeline. This is not a crude on/off toggle; it is a permission model that reflects the actual job functions in the business.\n\nRole assignment, permission editing, and user invitation all happen in-console without requiring a developer. An owner can onboard a new team member, assign their role, and have them logging into a scoped console view in minutes.\n\nThe payroll module handles time tracking and wage calculation for hourly and salaried staff, with pay period management and export to standard payroll formats. For a small business currently running payroll through a disconnected HR tool or a manual process, bringing time tracking and CRM activity into the same system means shift hours and client-facing work are visible together -- no more reconciling two separate logs to understand staffing efficiency.\n\nAll admin actions are audit-logged, so the owner can see who changed what, when, and from which session -- a baseline security and accountability requirement for businesses managing customer data.","status":"roadmap","verticals":["Med spas and clinics","Home services","Local SMBs","Private lenders"],"integrations":["Supabase Auth","CRM","Payment processor"],"replaces":["Gusto HR","Rippling","ADP Run","Separate HR/payroll tools"],"url":"https://y-infra.com/capabilities/admin-rbac-payroll"},{"id":"automation","name":"Automation -- Activepieces","llmSummary":"No-code automation fabric built on Activepieces (MIT) -- connects CRM, booking, email, your payment processor, and external tools with owned, self-hosted workflow automations.","description":"YInfra's automation fabric runs on Activepieces, an MIT-licensed no-code workflow platform that connects every surface inside the console and bridges to external tools without requiring custom integrations for each connection. Think of it as the connective tissue that makes the operating layer behave as a single system rather than a set of disconnected modules.\n\nExample automations that run out of the box: when a new lead form is submitted, create a CRM contact, score the lead, assign a follow-up task, and send a branded confirmation email -- all without a staff member touching the workflow. When a calendar booking is confirmed, update the CRM stage, schedule a reminder email 24 hours before, and log the appointment in the pipeline. When an invoice is paid through the payment processor, move the deal to Active in the pipeline and trigger a welcome email sequence.\n\nActivepieces supports hundreds of external app connectors -- Slack, Google Sheets, Zapier-compatible webhooks, and more -- so businesses can maintain the tools they need to keep while still routing data through the YInfra console as the operational hub. A Google Sheets-based reporting tool that an accountant depends on can receive CRM data exports on a schedule without any manual export step.\n\nBecause Activepieces is MIT-licensed and self-hosted, automation workflows are owned infrastructure -- not a monthly Zapier subscription that charges per task and goes up every time the business grows. Complex multi-step workflows with conditional logic, delays, and parallel branches are all supported.","status":"live","verticals":["All verticals"],"integrations":["Automation layer","CRM","Calendar / scheduling","Payment processor","React Email","Social publishing","Slack","Google Sheets"],"replaces":["Zapier","Make (Integromat)","n8n","GoHighLevel workflows","HubSpot automation"],"url":"https://y-infra.com/capabilities/automation"},{"id":"white-label-branding","name":"White-Label Branding","llmSummary":"Every surface -- console URL, emails, booking pages, payment links, invoices -- carries the client's brand, not YInfra's. Custom domain, logo, colors, and typography applied system-wide.","description":"White-label branding is not a theme switcher or a logo upload field -- it is the principle that every surface the client's team uses and every output the client's customers receive carries the client's brand, not YInfra's. The console a med spa's front desk logs into every morning should look like it belongs to the spa, not to the infrastructure vendor behind it.\n\nThis applies at every layer: the operator console URL runs on the client's domain (console.theirspa.com, not app.y-infra.com). The logo in the sidebar, the color palette of the UI, and the email templates all carry the client's visual identity. When a customer receives a booking confirmation, it is from the spa, not from a generic platform. When an invoice arrives in a client's inbox, it has the lender's letterhead, not a SaaS platform's branding.\n\nBranding configuration is set once at the infrastructure level and propagates automatically to all connected surfaces -- the console, outbound emails, booking confirmation pages, payment links, and any client-facing documents generated by the system. Updates to brand assets propagate system-wide without requiring per-surface edits.\n\nFor private lenders, white-label branding means a deal portal that looks like their firm, not a third-party tool -- giving investors and borrowers a professional, branded experience that signals operational maturity. For content creators, it means a client portal that carries the creator's identity, not a generic tool's interface.\n\nThis is the owned part of owned business infrastructure: the client's team uses a system that feels like it is theirs, and their customers interact with a brand experience that is completely consistent with every other touchpoint.","status":"live","verticals":["All verticals"],"integrations":["Next.js","React Email","Calendar / scheduling","Payment processor"],"replaces":["GoHighLevel white-label","Generic SaaS branding limits"],"url":"https://y-infra.com/capabilities/white-label-branding"},{"id":"app-development","name":"App Development","llmSummary":"Custom application development inside the owned operating layer -- bespoke customer-facing and internal apps built on the same data, auth, and brand as the console, scoped to the client's spec and owned by them.","description":"App development is where YInfra builds the part of a business that no off-the-shelf tool models well -- a specialized intake or quoting flow, an internal tool the team works in all day, or a customer-facing app -- as a first-class part of the owned operating layer rather than a separate subscription bolted on the side.\n\nBecause a custom app is built inside the console, it shares the same data, auth, and brand as everything else. A bespoke booking flow writes straight to the CRM; an internal dispatch board reads the same pipeline the owner sees; a field checklist updates the customer record in real time -- with no syncing between a third-party app builder and the system of record.\n\nThe point is the fewest moving parts. We don't rebuild what already works: the diagnostic decides where a custom app is clearly better than keeping or integrating an existing tool, and we build only that. What we build is scoped to the client's spec, owned by the client, and deployed on their own infrastructure (or a clearly scoped managed deployment with portable data).\n\nTypical builds include customer-facing apps tied to the operating layer, internal operations tools, specialized intake and quoting flows, and lightweight dashboards for a workflow a generic SaaS tool handles badly.","status":"live","verticals":["All verticals","Local SMBs","Private lenders","Content creators"],"integrations":["CRM","Pipeline","Automation layer","Supabase"],"replaces":["Off-the-shelf SaaS that only half-fits","No-code app builders (Bubble, Glide)","Disconnected internal tools","Spreadsheets standing in for software"],"url":"https://y-infra.com/capabilities/app-development"},{"id":"customer-portals","name":"Customer Portals","llmSummary":"Branded, on-domain customer portal where clients book, pay, sign, upload documents, and track status -- tied directly to the CRM, pipeline, and finance view so every action updates the operating record with no staff re-entry.","description":"A customer portal gives a business's clients one branded place to do the things they currently do across email, phone calls, and disconnected tools -- book and reschedule, view their history, pay invoices, upload documents, sign agreements, and check the status of work in progress.\n\nThe portal runs on the client's own domain and brand, not a third-party vendor's. Because it is part of the operating layer, every customer action updates the operating record directly: a booking lands in the pipeline, a payment posts to the finance view, an uploaded document attaches to the contact -- with no staff re-entry and no separate system for the team to reconcile.\n\nFor a med spa, the portal is where a client books a treatment, completes intake forms, and pays. For a private lender, it is a secure place for a borrower to submit documents and track deal status. For home services, it is where a customer approves a quote and sees the appointment. Each portal is scoped to the workflow that vertical actually needs.\n\nLike everything in the operating layer, the portal is owned by the client and assembled from the fewest moving parts -- replacing a stack of separate booking, payment, e-sign, and document-sharing tools with one branded surface the customer already trusts.","status":"live","verticals":["Med spas and clinics","Home services","Private lenders","Local SMBs","Content creators"],"integrations":["CRM","Pipeline","Calendar / scheduling","Payment processor","Branded Email"],"replaces":["Separate client portals","Email and phone back-and-forth","Standalone booking + payment + e-sign tools","Customer-facing spreadsheets and PDFs"],"url":"https://y-infra.com/capabilities/customer-portals"}]}