Who's behind this
Shanshan "Sasha" Ma
Founder, LevelOneAI
Shanshan "Sasha" Ma founded LevelOneAI in San Diego to take on the work people rebuild by hand between their systems: the supplier date that changed in email, the order that no longer matches what the customer was told.
Sasha spent years in UX research and product management on enterprise software teams, beside buyers chasing supplier exceptions, AP teams reconciling invoices by hand and operations managers rebuilding the same spreadsheet every month. The pattern never changed: the systems held the record, and capable people spent their days connecting it to what was actually happening. So her focus moved from designing the user experience to designing the work itself.
LevelOneAI starts with that work, not with the technology. Every order, PO and invoice carries a promise. When what's actually happening stops matching it, LevelOneAI turns it into work the team owns, with the evidence, what's at risk, the next step and the follow-up, until it's resolved. The ERP and CRM stay the systems of record, and nothing changes in them without approval.
The measure is the result in the business: problems caught while there's still time to act, ship dates kept, cash collected on time, audits passed.
Writing
Notes from the field on where workflows break, why the workaround always shows up, and what it takes to replace it without ripping out the systems underneath.
Build, Buy or Connect? One Supplier Delay, Three Ways to Handle It
The build vs. buy debate is easier when you run it on one real piece of work. A single supplier delay, handled three ways: build a tool, buy a tool, or connect the systems you already have. What each takes, who keeps it running, and what it still misses.
Read article GeneralFive Decisions That Decide Whether Your Software Supports the Work
Most companies don't have a systems problem. They have five decisions nobody made deliberately — and a lot of work still landing on people. A sequence for operations leaders who already own the software.
Read article GeneralYour AI Can Find the Client Information. But Can Your Team Act on It?
Connecting an AI assistant to your email, notes and CRM makes client information easier to find. It does not make the team able to act on it. The difference between a searchable inbox and shared operational knowledge.
Read article GeneralWhen a Shipment Goes Off Track, the Real Work Begins
Learn how logistics teams can reduce the manual work behind shipment delays, carrier follow-ups, and delivery exceptions without replacing their existing systems.
Read article GeneralHow to Integrate AI with Your Workflow Across a Multi-Site Manufacturing Group
For manufacturing groups that grow by acquisition: three AI workflows that repeat at every site, how to decide build vs buy, and what to require before you buy.
Read article GeneralHow to Incorporate AI Into Your Clients' Order-to-Cash Workflows, for ERP and APEX Partners
For Oracle ERP and APEX implementation partners: where AI fits in order exceptions, credit applications and customer onboarding, how to build it once and reuse it, and how to start with one pilot.
Read article GeneralHow to Integrate AI with Your Workflow Without Adding More Work, for Food Safety and Compliance Teams
How to integrate AI with your workflow when you work in food safety and compliance: connect the evidence you already have, catch exceptions early, keep people in charge of decisions, and start with one inbox.
Read article GeneralYour CRM Isn't Going Away. And Salespeople Still Don't Want to Do Data Entry.
AI sales assistants that need reps to feed them notes recreate the chore they were meant to remove. The better approach builds context from the email, calendar, CRM and quotes that already exist.
Read article GeneralYour ERP Says 2 Weeks. Your Supplier Takes 6. Which Number Is Your Team Planning Around?
When supplier performance changes but ERP lead times don't, production gets planned around a number nobody believes. How to spot the drift early and connect it to the orders at risk.
Read article GeneralBefore You Redesign Your ERP Workflow, Run This 30-Day Test
Have an ERP redesign proposal on your desk? Before you sign, audit where your delays actually start, sort the wish list, and pilot one fix. A practical 30-day test.
Read article GeneralThinking About Replacing Salesforce? Find the Part That Actually Hurts First.
Mid-sized companies often blame Salesforce for work that happens outside it. How to tell a CRM problem from a workflow problem, and what LevelOneAI does in either case.
Read article GeneralYour ERP Has the Production Data. So Why Is Everyone Still Scheduling in Spreadsheets?
When every department runs its own version of the production schedule, the problem may not be your ERP. It may be the work required to turn its data into a plan everyone can actually use.
Read article GeneralYou Might Not Need a Bigger ERP Yet
Growing past $5M, the chaos gets blamed on your systems. Often it's coordination, not records. How to tell which problem you have before signing an ERP project.
Read article GeneralVibe Coding Your Own Business System Is Easy. Keeping It Running Is the Hard Part.
An AI coding tool can build an order tracker in an afternoon. Keeping it right is the real job. Where the hidden maintenance lives, three questions to ask before you depend on a prototype, and what to build instead.
Read article GeneralYour ERP Wasn't Designed for Your Workflow — Customize the Software, or Retrain Your People?
Off-the-shelf ERP is designed for the average company, and you are not the average company. Customize the software until it fits, or retrain your people until they fit it — both charge a price nobody quotes upfront. Here is what each one really costs, and the third option.
Read article GeneralEvery Exception Becomes a Manual Investigation
The system handles the normal case. The exception becomes a person opening six tabs to reconstruct what happened. Why exceptions are the real work — and how they stop being investigations.
Read article GeneralWe're Constantly Chasing Suppliers, Customers and Internal Teams
Following up is not a job, but in most operations it has become the job. What people say about the chase, what it really costs, and how follow-ups become part of the work.
Read article GeneralWe Re-Enter the Same Information From One System Into Another
Double entry between systems is a tax on every order, and it never appears on a report. Why it happens, what it costs, and how the work stops being copied by hand.
Read article GeneralI Have to Check Three Systems to Know What's Happening
The status question that costs three tabs and a phone call. Why work that spans systems can never be answered from one place, and what changes when the answer lives in the work itself.
Read article GeneralOur ERP Says One Thing. The Spreadsheet Says Another.
When the system of record and the spreadsheet disagree, somebody has to decide which is true. That adjudication is a job nobody designed — and it is fixable.
Read article GeneralThe Latest Information Is Always Buried in Someone's Email
The current version of the truth is usually in a thread, not a system. Why that happens, what it costs, and how the context gets assembled around the work instead.
Read article GeneralWe Have One Person Who Knows How Everything Works
The person who holds the process in their head is not a strength. They are the system. What that costs, and how to move the knowledge into the work itself.
Read article GeneralThe System Handles the Normal Case. Everything Else Becomes Excel.
Spreadsheets are not a failure of discipline. They are where undesigned work goes. Why the exception always ends up in Excel, and what a designed home for it looks like.
Read article GeneralI Can't Get a Reliable Status Without Asking Someone
When status only exists in people's heads, every update costs an interruption. Why reliable status is a design problem, and how work reports its own state.
Read article GeneralWe Have a System for Everything Except Actually Getting the Work Done
The stack is complete: ERP, CRM, ticketing, project management, email, chat. And the work still has no home. Why tool coverage is not the same as work coverage.
Read article GeneralIntroducing Operations Workbench Starter: See Which Changes Put Your Orders at Risk
Operation Workbench Starter reads your email and the exports you already have, shows which changes put orders at risk, with the evidence, and stays with each one until it's resolved. Free for 30 days.
Read article GeneralThe Intelligence Can Be Probabilistic. The Workflow Shouldn't Be.
LLMs are probabilistic — which is exactly why they belong in the information work, and not in the part that changes the state of the business. Why so many agents stall the moment they touch real orders, invoices, and schedules, and how to split the work so probabilistic AI improves human decisions while deterministic software executes them.
Read article GeneralNobody Owns the Complete Operational State. So Somebody Becomes the Human Router.
Your CRM knows the customer. Your ERP knows the transaction. Engineering knows the design. Supply chain knows materials. Production knows capacity. Email, Excel, and Teams hold the latest exceptions. Nobody owns the complete operational state — so somebody becomes the human router. Why that gap exists, why the usual fixes miss it, and what has to exist instead.
Read article GeneralAI or Not AI Isn't the Question. The Workaround Is.
A buyer spends four hours a day reconciling supplier issues. The natural response is to automate the reconciliation — and that's potentially fantastic, and the wrong place to start. The real question is why the reconciliation exists at all.
Read article GeneralYour Spreadsheet Isn't the Problem. The Work Behind It Is.
HubSpot is making external data usable inside the CRM, and that's the right direction. But a spreadsheet isn't always a data source — sometimes it's an unofficial application holding a workflow your systems don't represent. Data connectivity is not workflow transformation.
Read article GeneralThe Problem Isn't the Software. It's Adoption. — Is That Actually True?
Every platform rollout ends the same way: adoption at 18%, another six figures on training, and a spreadsheet still running the process. Adoption isn't the problem — it's the symptom of a workflow nobody fixed.
Read article