Operational AI architecture, design, implementation, and training — for fulfillment companies.
Many clients.
One operation.
For founder-led fulfillment companies (3PLs) that receive, store, pick, pack, and ship for other brands.
Every client arrives with its own catalog, its own rules, and its own questions. I design and build the systems that keep that knowledge in the operation, with the team that will run them.
Book a 45-minute conversationBuilt around an established operation
Your warehouse system, carrier accounts, client integrations, and accounting are already in place. So are the people who know each account. The work is what happens between them.
The warehouse has a system.
The accounts have memory.
The warehouse system knows where every unit is. What it does not hold is how each client wants things done, what was promised in an email, and why last month’s invoice looked the way it did. That lives with the people who know the account. It tends to show in three places.
Every new client
is a new rulebook.
Catalogs, packaging requirements, carrier preferences, and integration details arrive as files and emails. Turning them into a working setup depends on one or two people who have done it before.
↘02 / Client questionsThe answer takes
three systems.
Where is this order, why is this count off, when was that shipment received. An account manager assembles each answer from the warehouse system, the carrier, and the inbox.
↘03 / Month endThe month closes
in a spreadsheet.
Storage, handling, special projects, and client reports are assembled by hand from exports. The questions that follow are answered the same way.
↘01 / Architecture and design
Start with the map.
Then choose the work.
We map how a client is onboarded, how a question gets answered, and how the month is closed: where the information lives, who touches it, and which decisions need a person. Tools are chosen after the map is drawn.
The work connects what is already in place. Replacing the warehouse system is not where a first engagement starts. Who may see which client’s information is settled in the design, before anything is built.
Architecture and design deliverable: an opportunity map with a recommended sequence and the reasoning behind it.
A fulfillment company
A 60-person fulfillment company: two warehouses, 45 client brands. Priority: answer client questions and set up new clients without routing each one through the two people who know every account.
Give the team one place for each client’s instructions.
Bring packing rules, receiving requirements, carrier preferences, and past exceptions into a maintained source library, kept separate for each client. Each answer shows the document it came from. A question without a source goes to the account manager.
Evaluate: answers checked against the client’s current instructions; gaps routed to a responsible person.Prepare the onboarding packet from what the client sends.
Test extraction against a small set of past onboardings. Confirm which details conflict across the client’s files and which setup decisions a person makes.
Evaluate: completeness and corrections during review.Send account managers the daily exceptions.
The warehouse system already produces an exceptions report. Schedule it for each account manager before building something new.
Next step: agree which exceptions a client should hear about, and from whom.02 / Implementation
Where fulfillment companies
usually start.
Six of the ten systems, grouped by the three pressures above. Each example shows what it is checked against, what a person decides, and what it connects to.
Sell your own products through several channels? There is a page for that ↗
03 / Training
The people who know
the accounts run it.
Training happens on the work the team recognizes: a real client question, a real onboarding, last month’s close. We practice the process, make the review steps understandable, and build an operating guide people can use next time.
Your team takes ownership of day-to-day use and contributes improvements on its own working information, with the configuration and support responsibilities documented.
Training deliverable / A working session and operating guide
Practice a real task.
Use the system on a request the team has handled before.
Learn what to check.
Inspect the result, its supporting information, and the decisions that need a person.
Leave with a reference.
A short operating guide, worked example, or agreed procedure to use next time.
I built systems so I could
sell the business.
I’m David Legisima, founder of Bexos. I’ve founded and sold three e-commerce businesses and spent more than two decades architecting custom business systems. The most recent, Ship My Orders, was a fulfillment company and a three-time Inc. 5000 honoree. I sold it in 2025.
So the work on this page is work I have seen from the inside: setting up a new client, answering for an order, closing the month. Bexos brings that experience into my work with AI: understanding how the operation runs, deciding what is worth improving, and building practical systems with the people who will use them.
An engagement shaped around the work
A clear scope
before you commit.
We begin with a 45-minute conversation about your priorities. If there’s a fit, I propose a defined first step with a clear deliverable and fee.
Where feasibility needs testing, we agree on a small assessment first. Implementation, training, and any ongoing support are specified in the proposal.
A few practical questions
Before we talk.
Do we need to replace our warehouse management system?
No. The starting point is the set of tools you already run. I review the tools, information, and access available, then identify what can be connected or improved. Any new software, limitations, or additional costs are discussed as part of the scope.
Is this a software product?
No. These are custom systems built for your company, around your information and your team. The proposal specifies deliverables, training, and any ongoing support. Data, deliverable, and runtime rights are defined in the agreement.
Can our clients use what we build?
That belongs in the design conversation. Who has access, to which client’s information, and under whose account are decisions made in the architecture and design phase, before anything is opened to a client.
Could we do this ourselves?
Yes. If someone on your team has the time and interest, learning and building internally may be a good route. I can help with a specific challenge, work alongside that person, or take on a defined build. We can discuss which approach suits your situation.
A 45-minute conversation
Where does the work
still depend on memory?
Bring an onboarding that took too long, a question only one account manager can answer, or a report someone rebuilds every month. I’ll help you connect it to a useful first step, from the foundation through to the team using it.
No preparation is required. If it helps, bring an example of something you want to improve, anything you have already tried, and who would use the result.