Care
$1,200a month
8 hours included
For a small instance that needs someone on call for fixes and the occasional change.
Response: Next business day
See the plansA senior Odoo developer on a monthly plan. I take over from partners who disappeared, back up your internal admin, and keep the fixes and features your business needs shipping.
The partner who built your Odoo stopped answering.
One admin knows how everything works, and they are stretched.
Every upgrade quote assumes a rebuild, so the upgrade never happens.
Small fixes sit for months because they are nobody's priority.
These are not emergencies. They are what happens when a live system has no regular developer.
Pick the hours that match your month. Every plan includes fixes, custom modules, integrations, upgrades and advice from the same senior developer.
$1,200a month
8 hours included
For a small instance that needs someone on call for fixes and the occasional change.
Response: Next business day
See the plans$2,400a month
20 hours included
For a business shipping changes every month that wants a priority, senior queue.
Response: Four business hours
See the plans$4,400a month
40 hours included
For a team that wants a named developer in the room every week.
Response: Two business hours
See the plansOverage is $125 an hour, agreed before the work starts. The full terms sit on the pricing page.
Email or Slack what is broken, what is missing and what your team keeps working around.
You get a written answer on what is a fix, what is a change and what needs its own quote, within your plan response time.
Changes go to staging first, are tested on your data, and go live only when you approve.
What changed, how to use it and what is next. Partner and Embedded plans include a call.
Fixes, custom modules, integrations, upgrades, data cleanup and advice all come out of the same plan hours. There is no separate quote for every small request.
Most plans start with a system someone else built. The first month is a takeover review, included in the plan.
Odoo.sh or your server, the repository, the integrations and the third-party apps.
The code, the customizations, the data model and what looks fragile.
What is broken, what is risky and what to fix first, in plain language.
We start on the highest-cost problem in your first month.
Distribution
Catalog sync to a vendor portal, order queue labels and a duplicate SKU cleanup. The nightly catalog update runs without a person, and scans resolve to the right product.
Read the studySpecialty vehicle manufacturing
Label printing fixed, a financing app made installable on every rebuild, and new tracking, reporting and calendar tools shipped into production.
Read the studyCall analytics
Phone-system data landed in Odoo, with call logging, filters and reporting for the team, delivered alongside the monthly plan.
Read the studyClients are small businesses and most prefer not to be named publicly. References are available on request, and I will put you in touch directly.

I'm Stephen Woodworth. I started Loomworks in Wake Forest, North Carolina. I have been the Odoo developer behind the same client systems, which is why the plan looks like this: one developer who knows your system, month after month, instead of a new team for every project. I scope the work, do the work, and answer for it. When a job needs more hands, a small team builds alongside me and I review every change.
More about StephenTime on your requests: reading code, writing and testing changes, and the calls and notes that go with them. Your monthly summary shows the hours used.
The first two hours over the plan are billed at $125 an hour. Anything larger gets a written estimate first, so there is no surprise invoice.
No. A monthly plan buys availability and priority for that month, not a bank of hours.
Care: next business day. Partner: four business hours. Embedded: two business hours. The response time starts when a request reaches the plan channel.
Yes. Most plans start with a takeover review: access, code, data and integrations read and written up before the first fix. You get the risk list before any change is made.
No. I work on Odoo.sh, your own server, and Odoo Online where the customization allows it. The plan does not require a move.
You do. Work is committed to your repository, with written notes for every change, and you can leave with everything.
Hosting and license fees, third-party app subscriptions, and project work large enough to need its own fixed quote. Those are billed by their providers or quoted separately.
Rarely. This is a support and development practice. If you have not started with Odoo, I will tell you honestly and point you to people who do that work well.
After the first 3 months, with 30 days notice. The plan runs month to month after that.
Pick a plan, or book a call and we will size it together.