Carry approved product knowledge, claims and commitments into every interaction.
Make answers clear, respect stated preferences and leave consequential decisions with the person.
The design goal: an agent that helps a relationship endure as communication scales.
They need to sell again to the customers they already have.
A campaign, a social post and a customer reply should carry the same product facts and approved claims.
Create content and flag unsupported claims before review.
Ground answers in product information and merchant policies.
Prepare relevant outreach and next steps for existing customers.
Connect customer data, product facts, approved claims and tone.
Prepare outreach and AI video. Review content against merchant rules.
Draft replies and sales next steps with the conversation in view.
Check the content, correct the context and approve the action.
An existing network of merchant relationships.
SlyOS offered under the partner’s branding.
Subscribes and connects its own customer database, product knowledge and policies.
Relevant outreach, repeat purchases and replies in one continuous workflow.
One merchant brings its customer context. Each new conversation improves what the merchant can understand and review.
15 AI videos monthly
15 video compliance checks monthly
300 outreach marketing emails monthly
45 videos + 45 checks shared monthly
+15 of each per additional paid seat
900 outreach marketing emails shared monthly
Subscription revenue less actual API usage and hosting costs, split with the partner and settled monthly.
Includes internal and test logins.
messages handled across 13 accounts
79% across 3 customer accounts, all time.
People have used the product to handle messages and send drafted replies.
Paid merchant pilots, repeat usage, retention and the cost to serve through a processor channel.
Marketing, outbound sales and inbound replies use the same merchant knowledge.
Processors already have the merchant relationship. SlyOS supplies the product under partner branding.
Readable state, controlled adaptation and evaluated routing are the path toward useful local intelligence.
General migration and the full phone learning loop still need proof.
Replies, reviewed content and outreach. Prove merchants keep using and paying for it.
Package the SDK. Evaluate learning, state transfer and safe routing against strong baselines.
Earn developer and device partnerships. Extend the agent across apps.
Build around the personal agent when the runtime and distribution justify it.
Built SlyOS and the SOUL research.
Stanford GSB Ignite
UC Riverside MBA
Mathematics & Economics
Enterprise software at Capgemini
Advisor
ML researcher in month 1.
ML engineer in month 3.
Business development in month 4.
Founder, specialist contractors and the new hires connect the research to merchant workflows.
SDK alpha and reproducible baseline comparisons.
Scope merchant pilots and processor onboarding.
Developer trials and bounded evaluation.
Measure reviewed outreach, replies and cost to serve.
SDK targets: 20 trials, 5 integrations, 3 paid pilots.
Validate merchant conversion, repeat use and partner economics.
of planned execution, plus contingency and cash reserves.
Founder, two ML hires and business development, with specialist contractors.
A developer-tested SDK and a paid merchant workflow with measurable repeat use.
First twelve months’ modeled cash deficit.
20% of fixed operating costs and capex.
Three months at modeled exit fixed spend.
$24K financing fees; remaining headroom.
First, better communication between merchants and their customers.
Then, the personal layer inside the operating system.