AI consulting and development services
AI consulting services for operations-heavy businesses: assessment, custom software, automation and security review, built into your systems.
We work with companies whose day runs through an ERP, one or more storefronts and the tools around them. We find where a model can take real effort out of that day, build the software around it, wire it into the system of record, and leave it running in your infrastructure with the records to show what it did. If you want the longer version of how we think about this, start with the guide to custom AI solutions for business.
Four services, each with its own page. Most engagements use two: an assessment to choose the first project, then a build or an automation to deliver it. The security review can also be bought alone, for a system we did not write.
Custom AI software development
For teams with a specific job in mind and no off-the-shelf tool that does it against their data. You get agents, copilots and automations, with the scheduler, approval queue and connectors they need, delivered as working software in your infrastructure with source and handover.
AI automation for ERP and ecommerce operations
For operations teams running Odoo, Shopify and the systems around them. Purchase planning, order intake, end-of-day reporting, wholesale shipping and support drafting, run on a schedule, written deterministically into the ERP, and released by a person. This is the work we know best.
AI strategy and opportunity assessment
For leadership teams who know AI should be doing something for them and do not yet know what to build first. A fixed-scope review of your workflows, data and systems that produces a ranked list of where a model pays off, in what order, with the integration work and the risk spelled out for each.
AI security review
For anyone about to put an AI system near their money or their customers. A review of its write paths, approvals, credentials, environment separation, data handling and model-provider boundaries, with written findings and a retest. It is not a certification and we say so plainly.
How engagements run
Every build follows the same four steps, aimed at a first system running in weeks, not quarters.
Scope
One workflow, named. The systems it reads, the one place it writes, who approves what, and the number we will watch to know it worked.
Build
Software in your infrastructure, under your credentials, with a staging environment that is separated from production from day one.
Review
Before anything can write to a live record, we audit the writes, the approvals and the secrets, and fix what we find. The security practices page describes what that covers.
Ship and run
Approval-gated at first, then widened as the records justify it. Documentation, handover and training so your team can run it without us.
The one system we can show end to end is Butler, built for PPC International, a Brdy Holdings portfolio company: internal work on a business we own, not an external client reference. The founding engagements page describes it on those terms.
Common questions
Do you only work with companies on Odoo and Shopify?
No. Odoo and Shopify are where we have the most hands-on experience, so our examples come from there. The same pattern applies to any ERP or ecommerce platform with an API, and we will say early in scoping if yours lacks the API surface the work needs.
Do you train AI models?
No. We build the system around a model: the connectors, the scheduling, the approval flow, the audit log and the deterministic code that actually writes to your records. The model itself comes from a provider, and the software is designed so the provider can be swapped or a local model used as a fallback.
Where does the software run and who owns it?
In your infrastructure, under your accounts and your credentials. You receive the source code, the database migrations and the documentation. Nothing we build depends on a subscription to us to keep running.
How does an engagement start?
With a scoping call about the workflow that costs the most manual effort, which systems it touches, and who approves what today. If an assessment is the right first step we say so; if one automation is obvious enough to build directly, we say that.
Tell us which workflow costs you the most.
A scoping conversation is the right place to find out whether any of this fits your operation, and which service to start with.
Book a call