Certification and your first project

You know the product and you understand projects. Nobody has paid you yet. This stage is about closing that gap.

What certification is actually worth

Honestly: it opens a first door and nothing more.

It gets your application read by a partner who has never heard of you. It gives a structure to your revision. It reassures a nervous first client. It does not get you hired on its own, and no experienced client has ever chosen a consultant because of it.

Sit it after you can configure a company from an empty database, not before. Certification obtained by memorising screens rather than by understanding fits nothing, and it shows in the first technical conversation.

Partner, freelance, or in-house

Route	Good for	The catch
Join an Odoo partner	Learning fast on real projects with someone senior to ask	Less money at first, less choice of work
In-house at a company using Odoo	Depth in one business, stable hours	You see one configuration, and can plateau
Freelance immediately	Independence and rates	You will make expensive mistakes alone, and clients pay for them

For nearly everyone starting out, joining a partner is the right first move. Two years there is worth five alone, because you see many businesses, you are corrected by someone experienced, and the mistakes are survivable.

Freelancing suits you later, or now if you already have a client who trusts you from a previous life. That is the most common way people start alone — an ex-employer, not a stranger.

Getting the first role with no portfolio

Nobody expects experience. They are looking for evidence you can think.

Build something real and show it. Configure a complete fictional company — a small distributor, a workshop, a services firm — with products, warehouses, taxes, users and a full document flow. Write the configuration notes. That is a portfolio, and almost no candidate brings one.

Write down what you learned. Public notes, posts, answers on the Odoo forum. Dated, searchable evidence that you understand things. It costs nothing and it is checkable.

Use the background you already have. You are not “junior” in the industry you came from. Someone from logistics who knows Odoo is more valuable to a logistics client than a generic consultant. Say so.

Apply to partners directly. Most of this hiring never reaches job boards. Find the partners in your country and write to them, naming what you have done rather than describing yourself as passionate.

Offer to help on a real project cheaply, once. Data migration, testing, training support. Unglamorous work is how you get into the room, and the room is where you learn.

Pricing a first engagement

If you are going straight to freelance, some plain guidance.

Do not compete on price. The client who chose you because you were cheapest will be your worst client, and will still expect everything.

Charge for days, not for the system. Price the analysis separately from the build. A paid discovery of a few days protects you both — you find out what the project really is before quoting it, and they get something useful even if they stop.

Never fix-price a scope you have not written. This is how beginners lose money. If they want a fixed price, do the paid discovery first, then fix-price what you have specified.

Put the boundaries in writing. What is included, what is not, how many training sessions, how long support lasts, what happens if their data is not ready on time.

Start smaller than you want to. One department, or one process, delivered properly, beats a full implementation you cannot finish. A finished small project produces a reference. An unfinished big one produces nothing.

The first project, realistically

Expect it to take longer than you estimated and to teach you more than a year of study. Expect the client’s data to be worse than promised, at least one requirement to have been misunderstood, and one thing to break at go-live.

That is normal. What matters:

• Say bad news early.
• Write down every decision.
• Deliver something that works, even if it is smaller than first discussed.
• Ask for the reference, and ask for it while they are pleased.

One delivered project with a client who will take a phone call about you is worth more than any certificate, any course, and any amount of further study.

Then keep learning

The product changes every year. So:

• Read the release notes each version and try the new features on a test database.
• Go deep in one area — manufacturing, finance, a localization — because specialists are paid better than generalists.
• Stay near other consultants. This job has no formal training after the start; you learn from people.
• Write down what you did. Your notes are your value, and they are how you avoid solving the same problem twice.

If you have followed this path to here, you are further along than most people who describe themselves as Odoo consultants. Go and do one real project.