Agreed scope, with a record.
Keep the version the customer approved, the materials they saw and any separately agreed additions connected to the work.
Signature and stage rules checked for the chosen documentsPre-Seed· Private beta· Founder-led pilots
From inquiry to approved work.
Conversations, agreed scope, jobs and customer documents in one context. AI helps prepare the next step; your team reviews important decisions. Founder-led pilots test one useful workflow before wider rollout.
Informational only. Not an offer to sell or a solicitation to purchase securities.
InquiryAgreed scopeWorkDocuments
Customer message · 10:42 AM
Can you help assemble two shelves? I can send photos and measurements.
Draft: Please send the photos and dimensions so our team can review the scope.
Operator reviews the next stepCheck the request, recipient and message before sending.
BazasOne context
ConversationEstimate draftCustomer portal
Stage
Pre-Seed
Product status
Private beta, founder-led onboarding
Availability varies by feature — see product status.
Initial customer
U.S. service businesses (1–20 field workers)
Business model
Subscription + usage; commercial validation pending
Go-to-market
Founder-led sales; selected agency workflows to validate
Operating company
Bazas AI LLC
Round
Terms are not publicly confirmed
Platforms
Web application
Private betaThe web workspace implements customer records, conversations, jobs, appointments, estimates, the core customer portal and selected invoice/payment processes. The current rollout is a closed, founder-led pilot: access, configuration and an agreed workflow are checked with each company before use.
iOS application
Internal TestFlightThe October 4 Apple snapshot showed build 91 in internal TestFlight. October 6 developer reports describe newer mobile work but do not verify the currently available Apple build or external access. The available build and its selected workflows need confirmation before an external pilot; full web parity and public App Store availability are not claimed.
Developer reports reviewed: Oct 6, 2026. Website copy updated Oct 7, 2026. Reports are distinct from independent runtime and external pilot acceptance; the dated Apple snapshot is not a latest-build claim.
The problem
Service businesses already pay for leads. They still lose them.
- A customer calls or sends a message.
- The owner or dispatcher is busy — driving, on-site, or with another customer.
- The response is delayed.
- The customer contacts the next provider.
- The business loses both the lead cost and the potential job revenue.
Missed calls
Calls arrive while the owner is driving, working on-site, or speaking with another customer.
Fragmented inboxes
Messages are spread across phone, SMS, email, Yelp, Thumbtack, web forms, and other channels.
Inconsistent follow-up
Important details are lost, quotes are delayed, and promising leads are forgotten.
What the leak looks like
Adjust the inputs for a rough sense of the money at stake when inbound isn't answered fast.
Estimated wasted lead spend / mo$613
Estimated missed opportunity / mo$2,363
Illustrative estimate only. This calculator does not represent actual or guaranteed Bazas customer results. Values are computed in your browser and are not sent anywhere.
The product
One context, from inquiry to approved work.
Connect the request, approved scope, work and customer documents. Important decisions remain reviewable; the closed pilot accepts the process your company will actually use.
Capture the inquiry
A verified channel brings the request into the right customer context.
Review the next step
AI helps draft; the operator checks the customer, action and recipient.
Agree the scope
Share an estimate, materials and any stages; retain the accepted version.
Run the work
Keep the appointment and job connected; agree additions separately.
Prepare the invoice
Review the drafted invoice and record confirmed funds through the chosen payment process.
Keep the customer informed
The customer returns to the company portal for the shared documents and next step.
A clearer customer experience.
A company-branded portal gives the customer a place to return to shared projects, documents and contact with the team.
Actions and link access accepted during onboardingMoney follows confirmed events.
Draft the invoice from agreed work. Record confirmed funds through the selected payment process; reconcile balances and receipts.
Payment notices and actual funds are separateScope and availability
Connected customer conversations
Supported messages, calls and email workflows stay connected to the customer and the work.
Availability & limits
Selected, configured web pilot workspaces. Connections differ by channel. Recipient, delivery and permissions are checked; a connected badge is not proof of receipt.
AI answering on a business line
A configured assistant can collect details and help agree a next step using the available business context.
Availability & limits
Configured number, hours and calendar. Booking and transfer to a person during business hours require scenario acceptance. New after-hours and interrupted-call handling is not presented as released.
Email in the customer history
Supported email workflows connect incoming messages to context and AI-assisted replies.
Availability & limits
A supported mailbox configured for the pilot. Current email setup is assisted. This is not self-service connection of any mailbox; provider access and delivery need checking.
Lead-source connections
Supported Yelp and Thumbtack workflows connect inquiries to CRM conversations.
Availability & limits
Set up and accepted per channel and account. Some routes use external automation. Capture, actual reply delivery and the handoff policy are evaluated separately; channel coverage is not universal.
Appointments & jobs
Keep the appointment, work and customer history connected without re-entering the agreed scope.
Availability & limits
Agreed web scheduling process. Business hours, time zone, availability and staff assignment are checked during onboarding. Voice scheduling has its own acceptance.
Human control of AI
Review Pilot's proposed customer and money actions, pause supported AI replies and continue the conversation yourself.
Availability & limits
Supported actions and configured reply policies. Pilot confirmation and separately authorised automation have different permissions. Conversation pause is not a blanket stop for every background process.
A shared context for the work
Connect inquiries, customers, approved scope, appointments, jobs and documents so the next step starts with the available history.
Availability & limits
Core web pilot process. The team sees information its permissions allow. Multiple-property and legacy-record behavior must be confirmed; a complete property-management rollout is not claimed.
Reviewable next steps
Review drafts, manage scheduled messages and track the next required action for a customer.
Availability & limits
Agreed policies, recipients and channels. Automatic sends need separate permission and acceptance. Scheduled status does not establish delivery or a guaranteed dispatch time.
Estimates customers can approve
Prepare a price range or agreed scope, attach customer-facing materials and retain the version the customer approved. Additional work has its own approval.
Availability & limits
Reported deployed web document process; acceptance required. AI prepares a draft; review and sending are distinct steps. Signature requirements, payment stages, templates, tax settings and the customer's actions are checked per pilot. Approval is not a legal-contract guarantee.
A clearer next step for your customer
A company-branded customer portal connects project information, shared documents and contact with the team through a link.
Availability & limits
Reported deployed web portal; setup and acceptance required. Available actions and link renewal are confirmed for the pilot. This does not promise all documents, unrestricted history, arbitrary rescheduling or a custom domain. Branding includes Bazas attribution; document and PDF languages vary.
Invoices & confirmed payments
Prepare an invoice from the agreed work and record confirmed payments, including selected manual and partial-payment processes.
Availability & limits
Chosen payment process after financial acceptance. A customer's 'sent' notice is not proof of funds. Balances, receipts and accounting allocation are accepted together. Payment links or your payment details are distinct from an embedded Bazas card checkout; one is not promised here.
QuickBooks connection
Reported implemented paths connect CRM invoices with QuickBooks and bring supported payment events back into the customer process.
Availability & limits
Optional connection for an agreed account and process. An account and setup are required; entity mapping, payment allocation, receipts and recovery need acceptance. QuickBooks is not required for every pilot and this is not tax filing.
iPhone trip recording
Automatic trip recording and a journal for reviewing business and personal travel are in closed testing.
Availability & limits
Selected internal TestFlight scenarios. Requires consent and iPhone location permissions. Detailed trips belong to their driver; managers do not receive another driver's private journal. Accuracy, gaps, vehicle matching and a real PDF/CSV export remain acceptance gates; no tax-ready report is claimed.
Expense information for review
Keep supported expense records and documents available for the business to review.
Availability & limits
A supported expense process agreed during onboarding. OCR, mailbox import, bank connections, tax calculations and each export require their own confirmation. The October 6 reports did not independently audit these workflows; tax filing is not offered.
Contractor & agency pilots
Explore an agreed workflow for passing work to a trusted contractor and following the information each participant is allowed to see.
Availability & limits
Limited scope agreed with the founder. Assignment, shared history, commission calculation, recorded obligation and actual settlement are separate acceptance steps. Hidden phone numbers, bypass prevention, a multi-company dispatcher and automatic payouts are not promised.
Calls from the CRM browser
A proposed dispatcher workflow uses a headset and the company's configured phone line.
Availability & limits
Not available as a released pilot capability. Requires real two-way audio, corporate Caller ID, call completion and role-access acceptance before release.
Expanded after-hours handling
Development aims to preserve details from after-hours and interrupted inquiries for a reviewed next action.
Availability & limits
A separate release and acceptance gate. Not a promise that any overnight call results in a callback, SMS or booking.
Embedded card checkout
An integrated customer card-payment flow is a later financial milestone.
Availability & limits
Not part of the current agreed pilot scope. Provider connection and full payment, receipt, refund and reconciliation acceptance are required; no release date is promised.
Scope reviewed against developer reports dated October 6, 2026 and the earlier source review. These are implementation reports, not a new independent runtime audit. Onboarding confirms deployment, configuration and acceptance for each company's chosen process.
Current pilot scope
Availability follows acceptance.
Core private-beta scope (5)
- Connected customer conversationsSelected, configured web pilot workspaces
- Appointments & jobsAgreed web scheduling process
- Human control of AISupported actions and configured reply policies
- A shared context for the workCore web pilot process
- Reviewable next stepsAgreed policies, recipients and channels
Setup & acceptance required (10)
- AI answering on a business lineConfigured number, hours and calendar
- Email in the customer historyA supported mailbox configured for the pilot
- Lead-source connectionsSet up and accepted per channel and account
- Estimates customers can approveReported deployed web document process; acceptance required
- A clearer next step for your customerReported deployed web portal; setup and acceptance required
- Invoices & confirmed paymentsChosen payment process after financial acceptance
- QuickBooks connectionOptional connection for an agreed account and process
- iPhone trip recordingSelected internal TestFlight scenarios
- Expense information for reviewA supported expense process agreed during onboarding
- Contractor & agency pilotsLimited scope agreed with the founder
Separate releases in development (2)
- Calls from the CRM browserNot available as a released pilot capability
- Expanded after-hours handlingA separate release and acceptance gate
Planned after acceptance (1)
- Embedded card checkoutNot part of the current agreed pilot scope
Product preview
Show the work, not a feature count.
An estimate and a customer portal make the connected document experience concrete. The captures below use a local component demo and fictional records.
Local component demo · fictional data
01
Review the proposed scope
02
Return to the shared documents
These images were captured from locally rendered product components with fictional demo records. Controls in screenshots are inactive. They show the interface concept and do not establish a live production workflow or an external customer's acceptance.
AI preparesTeam reviews & sendsCustomer decidesAgreed work stays connected
Request a scoped walkthrough
Review the actual workflow, its availability and the next acceptance gate with the founder.
Your AI dispatcher
Keep the whole job moving.
From the first enquiry to the final follow-up. Bazas connects the conversation, the work and the next decision — so your team can focus on the customer.
Rollout in progress
We are implementing this connected dispatcher experience. Start with an agreed pilot; expand automation as each workflow is checked with your company.
Choose how much to delegate
You review. You decide.
You stay in charge. AI follows the conversation, spots missing details and prepares the next step. Reviewing a suggestion does not send a message or change a booking.
1Enquiry2Agreed scope3Visit4Invoice5Confirmed payment6Aftercare
Illustrative workflow · rollout scope
Ask what matters. Remember what was agreed.
Use your services, pricing and the customer’s history. Collect only the missing essentials, keep promises visible and bring the next useful step to the team.
A new channel. The same conversation.
A marketplace enquiry can continue by SMS or email without losing its context. We are connecting source-specific rules, email threads and human handoff across supported channels.
Plan the visit around the real work.
Coordinate suitable technicians, availability, job duration and travel. Handle changes and cancellations, and alert a person when a decision or response is missing.
Turn agreement into clear documents.
Connect preliminary estimates, customer approval, attachments, additional work and the invoice. Keep the accepted scope visible instead of asking your team to enter it again.
Follow the payment. Not just the message.
A customer saying “paid” is not confirmed funds. Connect verified or manually recorded payments, balances and receipts; update reminders when the situation changes.
Stay helpful after the job.
Build a clear path for feedback, complaints and warranty questions. Keep service follow-up separate from marketing, and stop when there is no useful next action.
The right context for the next decision.
Five connected layers shape the dispatcher we are building. A company’s rules and a customer’s needs belong in the same decision.
- PlatformPermissions and action limits
- CompanyYour team and business rules
- ServiceScope, questions and pricing
- SourceThe rules for this enquiry
- RequestThe customer and what was agreed
Start with the scenario that fits your business
The rollout includes human-only work with optional AI suggestions, first replies, collecting details, consultation and estimates, booking for approval, automatic booking and an agreed full workflow. Custom combinations keep your approval points and individual pauses.
Dispatcher programme · October 7, 2026
Prove useful delegation, then expand it.
The October 7 founder-approved programme extends the existing CRM into a context-aware dispatcher. Product acceptance and commercial evidence remain separate from this implementation scope.
Acceptance sequence
- Suggestions without external actions
- Human-confirmed execution
- Limited agreed automation
- An accepted end-to-end workflow
What we will measure
- Recommendations accepted, edited or rejected
- Correct completed actions and delivery failures
- Useful response time and human effort
- Total cost per completed step, including setup and support
No new external customer results, measured savings or runtime acceptance are announced by this update.
Timing
Why now
The pilot tests whether connected communication and operational workflows are useful to small service businesses. These are working hypotheses, not quantified market findings.
Fast, useful responses may help businesses retain inbound inquiries.
Businesses that already pay for leads have a practical reason to measure missed inquiries.
Inbound demand is fragmented across calls, texts, email, and lead marketplaces.
AI-assisted responses can reduce repetitive work when tested against a company's actual services and constraints.
Modern APIs let voice, messaging, scheduling, and CRM connect in one workflow.
Founder-assisted pilots can compare support effort and software cost with the work saved.
We attach a primary source to any external market statistic before showing it, rather than citing round numbers.
Early evidence
We show evidence, not adjectives.
Traction figures carry a period, an as-of date, and a methodology. Until those are published, we state the stage honestly.
Founder-led pilot stage
Pilot counts, revenue and customer outcomes are not published here. Request the available evidence; any figures shared must include a reporting period, date and methodology.
Results to date come from Repair ASAP, the founder's own service business — a real-world operating test environment, i.e. internal operating validation, not yet independent third-party validation. Each published metric must be dated and sourced. See the evidence policy in the investor note.
Business model
Subscription revenue plus usage-based expansion.
A monthly subscription includes defined AI, voice, and messaging allowances. Revenue can expand through higher usage tiers, overages, additional users, and additional locations.
- Monthly subscription per business
- Included AI, voice & SMS allowances
- Usage overages beyond the plan allowance
- Higher usage tiers
- Additional users
- Additional locations
- Premium workflows
- Additional financial automation
- Agency & franchise plans
- Company branding & agency workflows
- Enterprise integrations
Usage economics expand revenue with adoption
Plans include AI, voice, and messaging allowances. As a business relies on Bazas more, revenue expands through higher tiers, overages, and added users or locations — usage-based expansion on top of the base subscription.
Blended gross margin and contribution economics are not published. Any investor figures must be backed by dated usage and cost evidence.
Only current and genuinely planned lines are shown. This describes the intended model, not verified current revenue or customer adoption. Request the available economics evidence; ARPA, margin and retention require dated data.
Market
Start with a useful process for a small service business.
Bazas starts with small U.S. service businesses, initially in New York City: an owner or a small team managing inquiries, quotes and work. Contractors and small agencies are additional pilot audiences with separately agreed scope.
Initial ICP
U.S.-based · NYC firstOwner or small field teamInbound calls and messagesA supported first inquiry channelMeaningful average job valueOwner or small dispatch teamFragmented toolsWilling to use AI-assisted workflows
Bottom-up sizing
- Count businesses in the selected verticals.
- Take a realistic share at the target size band.
- Apply a realistic annual revenue per account.
- That yields an initial serviceable revenue opportunity.
- Expand later through multi-location, agencies, and franchises.
Target businesses × expected annual revenue per account = serviceable revenue opportunity
We do not claim the entire SMB or global AI market. The sizing method is bottom-up; numeric inputs and a sourced market estimate are not yet published.
Go-to-market
Founder-led today; repeatable and channel-driven next.
Phase 1 — Founder-led
Live- Fit interview and agreed scope
- Founder-assisted pilot access
- Verified channel and roles
- Human-reviewed AI replies
- Weekly feedback and support
- Measure usefulness and onboarding effort
Phase 2 — Repeatable vertical motion
Planned- Vertical playbooks
- Outbound
- Referrals
- Agency partnerships
- Industry communities
- Integration partners
Phase 3 — Channel expansion
Planned- Marketing agencies
- Franchise networks
- Multi-location operators
- Agency workflow partners
- Lead-gen platforms
- Telecom partners
Channel statuses are stated honestly: a relationship counts as a partnership only when it is live, not when there is potential interest.
Land & expand
Land on inbound. Expand into the system of record.
1Connected inquiry
2Reviewed next step
3Approved scope
4Work and documents
5Confirmed financial result
6Repeated daily use
Capture supported inquiriesPrepare a useful next stepAgree the scopeShare customer documents
Connected customer portalAccepted financial processesReviewed field workflowsPartner assignmentsDispatcher toolsFurther integrations
Expansion is intended to increase retention, switching costs, ARPA, and data quality. These are goals, not yet proven — switching costs depend on retention data we are still gathering.
Competition
What the customer can choose instead.
The practical comparison is how a business handles one complete process. Capabilities vary by provider, plan and configuration; no blanket category score is assigned here.
A field-service suite
Keep operational work in an established suite and evaluate its communication and AI options.
Question to test
Can the chosen plan connect the inquiry, agreed scope and customer-facing documents in the process the team needs?
A separate AI receptionist
Add an assistant to the business line while the existing system handles work and documents.
Question to test
How are the captured details, calendar actions and human handoff verified in the operating system?
A human answering or office service
A person handles customer communication using the business's tools and procedures.
Question to test
How do notes, approvals and follow-up remain visible when the inquiry becomes a job?
A stack of specialist tools
Use the phone, inbox, calendar, documents and accounting applications already in place.
Question to test
Who transfers the context and checks discrepancies between those tools?
A Bazas founder-led pilot
Agree one connected customer process, configure the supported channels and retain human review of important actions.
Question to test
Does an external company complete the agreed process reliably, return to it and find enough value to pay?
These are alternatives to evaluate, not audited feature claims about a vendor or category. Bazas must earn the choice through observed usefulness, reliability, cost and repeat use.
Reasons to keep an existing setup
- Existing tools and habits can already serve a business well
- Mature products may offer a broader feature set and established support
- A migration needs a practical benefit and an acceptable setup cost
The Bazas proposition to validate
- Available customer context follows the inquiry into agreed work and documents
- AI prepares the next step with explicit human review and configured permissions
- Customer-facing documents and the portal remain connected to the operating process
- A founder-led pilot accepts the chosen workflow before adding automation
Defensibility
A path to durable value, still to be proved.
Connected operating context
Customer history, agreed scope, corrections and next steps become useful when the team repeatedly relies on them.
Accepted workflows
Company-specific setup and checks can become repeatable playbooks as independent pilots reveal common needs.
Embedded connections
Supported channels, documents, calendars and accounting paths must work together beyond a configured badge.
Distribution
Contractors and small agencies may create a repeatable route to the next business after a successful pilot.
Trust & control
Reliable results, role access, reviewed AI actions and a responsive support loop give users a reason to return.
Evidence from use
Retention, willingness to pay and support economics test whether the product is becoming part of daily work.
These are potential sources of defensibility. Retention, switching costs and a lasting competitive advantage are not yet independently established.
Founder–market fit
Built from inside the workflow.
Bazas was founded by Nikita Lylov, an economist and service-business operator who has worked with CRM systems since 2011—first in sales, later as an entrepreneur and business owner, and now as the founder and product builder behind Bazas.
After launching Repair ASAP, a home-services company in New York City, he experienced the problem firsthand: paid leads arriving while the team was out on jobs, conversations fragmented across calls, SMS, email, Yelp, and Thumbtack, and valuable customer context getting lost between first contact, booking, and follow-up.
Bazas was developed and tested inside that live operating workflow. Repair ASAP—a founder-operated service business—is Bazas's first operating customer and real-world test environment. Bazas is a separate SaaS platform being built for the broader service-business market.
Working with CRM systems since 2011 across sales, entrepreneurship, and home-services operations. Built Bazas from a live operating business and continues to test it against real leads, calls, bookings, and follow-up workflows.
Bazas is founder-led today. The Pre-Seed round is intended to support key hires across product, engineering, security, and customer success.
Roadmap
Earn the next stage through real use.
Now · agree one useful process
- Closed web pilots with founder-led fit and setup
- Connected inquiries, agreed documents, work and the core portal
- Human-reviewed AI actions and confirmed channel permissions
- Chosen internal iPhone scenarios; current build checked separately
- Define the payment process, support contact and result to measure
- Implement context-aware dispatcher suggestions without external actions
Next · prove repeatable use
- An external company completes the agreed process
- Accept dispatcher suggestions, human-confirmed execution and limited source-specific automation
- Amounts, confirmed payments, receipts and accounting allocation reconcile
- Real trip distances and a first accepted PDF/CSV export
- Repeatable onboarding, role checks and issue tracking
- Measure recommendation acceptance, useful response time and total cost per completed step
- Accept phone recipients, after-hours handling and browser calls as separate releases
Later · expand from evidence
- Embedded card checkout after payment acceptance
- Multi-company dispatch and broader contractor settlements
- Expand accepted dispatcher workflows through confirmed payments, aftercare and warranty handling
- Broader integrations and field workflows chosen from pilot demand
- External mobile distribution and public App Store release after their gates
- Self-service onboarding once setup and support are repeatable
What the next pilot phase must prove
One accepted external customer process
ProductSuccess: The pilot company completes inquiry → approved scope → work → reviewed invoice through the agreed payment process, without a developer repairing its data.
Phase: Initial closed pilot
Requires: Verified access, delivery, AI permissions and financial scope
Consistent money and documents
ProductSuccess: Selected full, partial and repeated payment cases leave matching balances, accepted receipts and correct accounting allocation.
Phase: Before financial pilot acceptance
Requires: Chosen payment method and optional accounting connection
A traceable support loop
CustomerSuccess: A reported problem has a reference, company, owner, priority, status and visible next action or confirmed resolution.
Phase: Initial closed pilot
Requires: Working support intake and notifications
Repeatable onboarding and access
ProductSuccess: A second company can be connected from a checklist; record setup time, required assistance, isolation, roles and recovery checks.
Phase: Following pilot companies
Requires: Accepted first process and clear pilot limits
A field workflow accepted on a real device
ProductSuccess: Confirm the available iPhone build, compare real trips with the route and accept a real export in the chosen mileage scope.
Phase: Selected mobile pilot
Requires: Device distribution, consent and a defined testing period
Useful adoption and paid continuation
CommercialSuccess: Measure completed useful processes, repeat use, reasons to stop and willingness to continue on clear paid terms. Keep free access separate from paid customers.
Phase: External pilot validation
Requires: Reliable onboarding and support
Economics backed by operating evidence
EconomicsSuccess: Record AI, phone, infrastructure, setup and support cost per active company, alongside the verified revenue period.
Phase: Pilot validation
Requires: Dated usage, cost and payment evidence
Funding attached to the next outcome
TeamSuccess: A dated demonstration, external pilot evidence, cost model and next acceptance goal support the budget and hiring plan.
Phase: Investor diligence
Requires: Founder-approved budget and evidence packet
Delivery sequence
Progress means a usable result.
Each milestone has a clear acceptance goal. An engineering task becoming complete does not automatically make a workflow available to customers.
A dependable customer processPriorities 1–6
A focused first workflow
In progressAcceptance: A defined customer, main channel and useful result.
Data access and recovery
In progressAcceptance: Company and role access, link revocation and recovery checked for the pilot.
Confirmed payments and consistent documents
In progressAcceptance: Invoices, confirmed payments, balances and receipts agree in the selected workflow.
Reliable enquiries and replies
In progressAcceptance: An enquiry reaches the correct company and the operator can verify the reply result.
Human control over AI actions
In progressAcceptance: Review, pause and human handoff work for the agreed channels.
One complete customer workflow
In progressAcceptance: The agreed process is repeated without a developer repairing business records.
Repeatable use and evidencePriorities 7–13
Support and visible issues
In progressAcceptance: Issues have a reference, owner and status; the team sees critical failures.
Repeatable company setup
In progressAcceptance: A second company can be connected using a defined setup and exit process.
Clear customer documents and portal
In progressAcceptance: Customers can review the intended documents and recover link access on mobile.
A clear next step for the team
In progressAcceptance: The operator can identify pending decisions and next actions in daily use.
Independent company pilots
PlannedAcceptance: External companies repeat a useful workflow and return to use it.
Measured costs and willingness to pay
PlannedAcceptance: Usage, setup and support costs are measured and a paid continuation is tested.
Evidence for the next investment milestone
In progressAcceptance: The demo, actual results, costs and next measurable outcome are documented.
Field and partner acceptancePriorities 14–17
Accepted iPhone workflows
In progressAcceptance: The available build and selected workflows are checked on a physical device.
Reviewed trips and a real mileage export
In progressAcceptance: Trips are compared with real journeys and a useful PDF or CSV export is accepted.
A two-company partner workflow
In progressAcceptance: Assignment, access, shared work and agreed terms are accepted separately from payouts.
New calling and dispatcher workflows
In progressAcceptance: Calling, business line identity, hours, handoff and access are accepted for each release.
Expansion after validationPriority 18
Broader integrations and self-service
PlannedAcceptance: Expansion follows repeatable setup, support and validated customer demand.
Sequence reviewed 2026-10-07. October 6 developer reports and the October 7 founder-approved dispatcher scope; company-specific acceptance is still required. Completed acceptance is reported with scope and evidence; these goals do not announce a release date or a completed external pilot.
The round
We're raising a Pre-Seed round.
- Company stage: Pre-Seed, founder-led, private beta.
- The round funds the milestones below and the use-of-funds categories shown.
- Round terms are shared with qualified investors after securities-counsel review.
Round details available to qualified investors. This is not an offer to sell securities.
Use of funds
Category intent shown below. Exact percentages and dollar amounts are set once the budget is approved and are shared with qualified investors.
| Product & engineering | Reliability, integrations, and onboarding. |
| Customer onboarding & success | Get pilots live and retained. |
| Go-to-market experiments | Find a repeatable acquisition channel. |
| Infrastructure & AI/telephony | Voice, messaging, and inference at target cost. |
| Legal & compliance | Corporate, securities, and data compliance. |
| Security | Tenant isolation, audit, and vendor review. |
| Operating reserve | Runway buffer. |
Key risks
The risks, in plain sight.
Mitigations reduce risk. They do not eliminate it.
Product reliability
ProductAI can misunderstand an inquiry, and connected channels or documents can fail to deliver the expected result. The selected process needs real acceptance and a visible recovery path.
Mitigation
Owner-defined rulesHuman escalationTranscript reviewMonitoringRestricted actionsAudit logs
Customer adoption
MarketIndependent companies may not find enough everyday value, trust the AI or accept the setup effort. Usage in the founder's business does not establish external adoption.
Mitigation
Founder-led onboardingPreview modeApproval workflowsHuman takeoverGradual automation
Competition
MarketMature FSM and AI-receptionist companies could add similar capabilities.
Mitigation
FocusVertical workflowsIntegrationsCustomer contextChannel partnerships
Unit economics
EconomicsVoice, SMS, AI, and support costs could compress gross margin.
Mitigation
Usage-based pricingCost monitoringModel routingCachingWorkflow optimizationPlan limits
Platform dependency
TechnicalBazas depends on third-party APIs, telecom, messaging, and lead-source integrations.
Mitigation
Provider abstractionBackupsMulti-provider where practicalGraceful degradation
Execution risk
CompanyA Pre-Seed company has limited team and capital.
Mitigation
Narrow initial ICPStaged roadmapMeasurable milestonesControlled onboarding
Data & privacy
SecurityThe system processes conversations and customer data.
Mitigation
EncryptionAccess controlsTenant isolationRetention policiesAudit logsVendor review
Fundraising risk
CompanyA future round may not close on the desired timeline or terms.
Mitigation
Capital efficiencyMilestone-based hiringRevenue focusRunway monitoring
FAQ
Investor questions, answered.
What exactly does Bazas do?
Bazas connects supported customer conversations, agreed scope, jobs and customer documents. AI helps prepare drafts and next actions; the team reviews important decisions. A founder-led pilot starts with one useful, configured process.
Who is the initial customer?
Small U.S. service businesses, initially in New York City, whose owners or teams manage customer inquiries, quotes and field work. Contractors and small agencies can discuss a limited partner pilot with separately agreed access and terms.
What is live today?
Developer reports reviewed October 6 describe implemented web records, conversations, jobs, estimates, core portal and selected payment processes. Deployment and acceptance for a new company are checked separately. The October 4 Apple snapshot showed internal TestFlight build 91; it does not establish the current available build or external distribution. No public App Store release is claimed.
What is still in beta?
Most of the inbound workflow — voice answering, messaging intake, qualification, booking, and CRM memory — is in private beta with selected pilot customers.
Does Bazas replace office staff?
The pilot is designed to assist a team. A configured assistant can collect inquiry details; supported human handoff and pause behavior are checked for the agreed channels. The team keeps responsibility for important customer decisions.
Can a business take over a conversation?
Human review and takeover are core design principles. The pilot verifies which supported conversations can be paused and continued by an authorised operator. A conversation pause is not a guarantee that every unrelated background action stops.
How does Bazas avoid incorrect bookings?
The pilot verifies hours, time zone, calendar availability and the company's booking process. Voice automation needs a separate acceptance pass. Service-area configuration does not certify that every booking path blocks out-of-area requests.
Which channels does Bazas support?
Supported calls, SMS, mailbox and lead-source workflows can be configured during onboarding. Requirements differ: a phone line, selected mailbox or external automation may be needed. Each pilot checks inquiry capture, recipient and actual delivery for its chosen channels.
What can a customer do in the portal?
The core portal connects intended project information, shared documents and contact with the company through a link. Actions, link renewal and document access are checked during onboarding. Custom domains, arbitrary rescheduling and a complete contract module are not promised. Company branding retains Bazas attribution; product and PDF language coverage differs from the marketing website.
Can customers pay by card inside Bazas?
An embedded Bazas card checkout is planned, not part of the current pilot offer. A chosen process may use your payment details or a supported external payment link. A customer marking a transfer as sent does not confirm funds; invoices, confirmed payments, balances, receipts and optional accounting allocation are accepted together.
Is automatic mileage ready for tax reporting?
Automatic iPhone trip recording is in closed testing with consent and location permissions. Detailed trips are private to their driver. Real distance, gaps, vehicle matching and the first accepted PDF/CSV export remain gates. A tax-ready report or tax filing is not claimed.
Is the contractor network an automatic payout system?
No. A limited assignment and shared-work pilot can be discussed with the founder. Commission calculation, a recorded obligation, actual money collection and payout are separate results. The site does not promise universal phone masking, prevention of bypass or automatic settlements.
What is still being developed?
Browser calls from a company line and expanded after-hours handling require separate releases and live acceptance. Later milestones include embedded card checkout, broader dispatcher and settlement workflows, and self-service onboarding. The roadmap records acceptance goals; code completion does not automatically promote a public claim.
How does Bazas make money?
A monthly subscription that includes defined AI, voice, and messaging allowances. Revenue expands through higher usage tiers, overages, additional users, and additional locations — with additional automation and integrations over time. Selected invoicing and payment processes are reported implemented; consistency of balances, receipts and accounting needs pilot-specific acceptance. Current revenue and economics are not publicly verified here.
What is the current pricing model?
Subscription plus usage. Public plan details live on bazas.ai. Request the available economics evidence; public plan descriptions do not verify current revenue or margins.
What is the current company stage?
Pre-Seed, founder-led, in private beta.
Is Bazas generating revenue?
Revenue status is shared with qualified investors. The public site does not display unverified financial figures; request the currently available evidence; any figures shared must be dated and sourced.
How many pilot customers are active?
The current count and related metrics are shared with qualified investors with an as-of date and methodology.
What is the go-to-market strategy?
Founder-led sales today, moving to repeatable vertical playbooks and then channel partners (agencies, franchises, multi-location and agency workflows).
Who are the main competitors?
Field service management suites, CRMs, AI receptionists, human answering services, DIY stacks, and in-house staff. The alternatives section explains the questions a buyer should test. It is not an audited feature ranking of entire categories or particular vendors.
Why won't established CRM companies simply copy this?
They may add similar features. Our intended edge is focus, an AI-native inbound workflow, owner-defined rules, unified context, and vertical playbooks — advantages we are still proving.
What is the long-term product vision?
An operating system for small and mid-sized service businesses — starting at inbound and expanding into the system of record.
What legal entity is raising the round?
Bazas AI LLC is the operating company. The definitive issuing entity for any offering — which may be Bazas AI LLC or a related entity — is set out in the offering documents provided to qualified investors.
Who owns the intellectual property?
Corporate and IP documents are requested individually. Their availability and completion must be confirmed before diligence.
What investment instrument is being used?
Instrument and round terms are shared only with qualified investors and only after securities-counsel review.
How will the funds be used?
Product and engineering, onboarding and success, go-to-market experiments, infrastructure, legal/compliance, security, and an operating reserve. Category intent is shown; exact allocation is shared with investors.
What must the company prove before the next round?
Reliable inbound workflows, measurable customer outcomes, a repeatable acquisition channel, and measured contribution economics; numeric targets follow observed pilot data. See milestones.
What are the primary risks?
Product reliability, adoption, competition, unit economics, platform dependency, execution, data/privacy, and fundraising. See the risks section — we do not hide them.
How can an investor access the data room?
Request materials through the form. Access is reviewed individually and may require identity or investor-status verification.
How frequently are investor materials updated?
Materials carry a last-updated date. Investor updates are posted as milestones are reached.
Is the information on this website an investment offer?
No. This website is for informational purposes only and is not an offer to sell or a solicitation to buy securities. Any offering, if made, will be conducted only through definitive offering documents and in accordance with applicable law.
Review the product, evidence, and current round materials.
Requests are reviewed individually. Access to certain materials may require identity or investor-status verification.