Loomworks Solutions
PlansWhat we doHow it worksResultsAbout
Book a call

Plans

  • Plans and prices
  • How it works
  • Book a call
  • Questions

What a plan covers

  • Custom modules
  • Version upgrades
  • Data cleanup
  • Integrations
  • Rescue reviews and second opinions

Proof

  • Results
  • About
  • Blog
Loomworks Solutions LLC
Wake Forest, North Carolina·984-251-1753·stephen@loomworks.solutions
GitHub (opens in new tab)
© 2026 Loomworks Solutions LLC. All rights reserved.
Privacy policyTerms of serviceSMS consentSign In

Odoo support that knows your system.

A 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.

Book a callSee the plans
  • 30 minutes, free, on the phone or video.
  • Three plans, priced by the month.

Sound familiar?

  • 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.

One plan, three sizes

Pick the hours that match your month. Every plan includes fixes, custom modules, integrations, upgrades and advice from the same senior developer.

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 plans

Partner

Most popular

$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

Embedded

$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 plans

Overage is $125 an hour, agreed before the work starts. The full terms sit on the pricing page.

Book a callSee the plans

What a month looks like

  1. Send the list

    Email or Slack what is broken, what is missing and what your team keeps working around.

  2. I triage it

    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.

  3. We build it

    Changes go to staging first, are tested on your data, and go live only when you approve.

  4. You get the notes

    What changed, how to use it and what is next. Partner and Embedded plans include a call.

What is included

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.

  • +Fixes on your live system. Bugs, blocked screens and the small breaks that slow a team down.
  • +Custom modules and changes. The step standard Odoo misses, built as a module that survives the next upgrade.
  • +Integrations. Shipping, ecommerce, accounting and document tools connected to Odoo.
  • +Version upgrades. Planned and rehearsed, with your customizations carried forward.
  • +Data cleanup and reports. Duplicates, reconciliations and the reports your team asks for.
  • +Advice, by message or call. A senior answer before you commit to a change, inside your plan hours.

Taking over from another partner

Most plans start with a system someone else built. The first month is a takeover review, included in the plan.

  1. Access and inventory

    Odoo.sh or your server, the repository, the integrations and the third-party apps.

  2. Read the system

    The code, the customizations, the data model and what looks fragile.

  3. Written risk list

    What is broken, what is risky and what to fix first, in plain language.

  4. First fixes

    We start on the highest-cost problem in your first month.

See how the takeover works

What this looks like when it is done

Distribution

A fabric distributor, on an ongoing plan.

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 study

Specialty vehicle manufacturing

A van upfitter, on ongoing support.

Label printing fixed, a financing app made installable on every rebuild, and new tracking, reporting and calendar tools shipped into production.

Read the study

Call analytics

A call analytics company, on ongoing development.

Phone-system data landed in Odoo, with call logging, filters and reporting for the team, delivered alongside the monthly plan.

Read the study

Clients are small businesses and most prefer not to be named publicly. References are available on request, and I will put you in touch directly.

Who this is for

This is for you if

  • +Odoo is live and the partner who built it is gone, unresponsive, or quotes a rebuild for every change.
  • +You have an Odoo admin or small IT team and need a senior developer to back them up.
  • +You are on Odoo v12 to v19 and need someone who has done upgrades and custom modules.

This is not for you if

  • -You have not chosen an ERP yet. A first implementation is a different job.
  • -You need a full-time employee.
  • -You are shopping for the lowest hourly rate.

Who you'll be working with

Stephen Woodworth

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.

Wake Forest, North CarolinaOdoo Community Association memberGitHub
More about Stephen

Straight answers

What counts as an hour?

Time 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.

What happens if we go over the plan hours?

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.

Do unused hours roll over?

No. A monthly plan buys availability and priority for that month, not a bank of hours.

How fast will you respond?

Care: next business day. Partner: four business hours. Embedded: two business hours. The response time starts when a request reaches the plan channel.

Can you take over from our current partner?

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.

Do we have to move hosting or change our Odoo edition?

No. I work on Odoo.sh, your own server, and Odoo Online where the customization allows it. The plan does not require a move.

Who owns the code and the data?

You do. Work is committed to your repository, with written notes for every change, and you can leave with everything.

What is not included?

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.

Do you take on new Odoo implementations?

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.

Can we cancel?

After the first 3 months, with 30 days notice. The plan runs month to month after that.

Book a callSee the plans
All questions

Tell me what your Odoo should be doing. I'll tell you what a monthly plan would take.

Pick a plan, or book a call and we will size it together.

Book a callSee the plans