Freelancer or agency? The question that counts is experience with WhatsApp

We are an agency, so read this knowing that. We just think you are selecting on the wrong attribute.

Jamal CederMeta Tech Provider · Updated September 2026 · 7 min read

Meta Tech Provider

Whether you hire a freelancer or an agency matters less than whether they have had WhatsApp live before. Projects that stall rarely stall on the software. They stall on Meta: business verification that is not done, templates that get rejected, a number stuck at its starting limit, or messages landing in the wrong category and costing double. Anyone who has been through that plans for it and budgets time. Anyone who has not discovers it halfway, and then it costs money or it never goes live at all.

What a freelancer does well

Most of this kind of job is just software. Read your system, transform data, filter it, connect it, build a screen where someone can switch something on. A good independent developer handles that fine, usually faster and always cheaper than we are.

If the scope is clear and someone on your side steers the project, that is the sensible route. We say so when someone calls us about it.

It goes wrong on the part that looks simple from the outside: the sending itself. That is not engineering but a set of Meta rules, and those rules punish inexperience with delay and with money.

What goes wrong when nobody has done it before

Spend an hour searching and you will find thousands of people who got stuck here. It is always the same four places.

1
Business verification is not arranged
Meta wants proof your company exists before you can send at any scale. That takes calendar time and can stall on a document that does not match the chamber of commerce record. Start it at the end and you are standing still with a finished integration.
2
Templates get rejected or land in the wrong category
Outside a running conversation you can only send an approved template, and the category decides what it costs per message. A utility message classified as marketing costs you a multiple across your entire list.
3
Your number stays stuck at its starting limit
Meta starts you at 250 unique contacts per 24 hours and only raises it once your messages are received well. If the first campaign sends something people swipe away, you are stuck while your list is larger than that limit.
4
The 24-hour window is not in the flow
The moment a customer messages you, you can reply freely for 24 hours, and after that only with a template. Build without that in mind and the conversation stalls on day two while nobody understands why.

What experience actually looks like

Experience here is not a feeling, it is an order of operations. This is what someone who has done it before does.

1
Verification is step one or two, not step ten
Creating the Meta Business account and getting the company verified happens before a line of code exists. Then Meta’s waiting time runs alongside the build instead of after it.
2
The messaging model drives the design, not the other way round
Knowing which message types exist and when to use which saves money directly. The same message can be free or expensive depending on when you send it and the category it falls into.
3
The plan has time in it for what routinely goes wrong
A rejected template, a verification asking for one more document, a limit that lifts later than hoped. Those are not setbacks, they are the normal course of things, and they belong in the schedule.
4
It starts small and scales after that
Part of the list first, watch how the messages are received, and only then build volume. Anyone who wants to message your whole list on day one has not done it before.
5
There is a line to Meta itself
A business on the API by itself falls back on documentation, the developer forum and a bug report. No chat, no phone. Parties with partner status can open a Direct Support ticket, and we are one of those. When a verification stalls or a template is rejected without a clear reason, we put it there instead of guessing and resubmitting.

And when WhatsApp is only a small part of your project

Sometimes WhatsApp is one percent of what you are having built and the rest is your own software. Then the scale tips the other way. The question becomes whether someone has built your kind of system and your kind of process before, because that is where your risk sits.

In that case choose on experience with your use case, not on experience with WhatsApp. And if the last stretch does stall on Meta, bring in someone who knows that part. It is a small job and it is quickly arranged.

We work that way in reverse too. When someone calls with a question where WhatsApp is the smallest component, we say we are not the obvious party.

Six questions to ask any builder

Including us. Ask them open, without building the answers into the question. What someone raises unprompted says more than whether they nod along with your list.

1
What do you watch out for in a WhatsApp Business implementation?
The most important question, and deliberately broad. Someone who has done it before starts on verification, on template categories and on the number’s quality rating. Someone who has not starts on the API.
2
Have you taken a WhatsApp number live before, and what went wrong?
The second half is the real question. Someone with experience has a story about a rejected template or a verification that stalled. Someone without says it went fine.
3
When do we arrange business verification?
The right answer is immediately, in the first week. If that answer arrives at go-live, your go-live moves with Meta’s waiting time.
4
Do you build on the official Cloud API?
The answer has to be yes. An integration through a browser bot or a second phone works until Meta notices, and then your number is gone.
5
How do I see whether a message arrived and was read?
Ask for the screen, not the promise. If delivered and read are not there per message, you cannot check anything afterwards and you cannot improve anything.
6
Who adjusts it when Meta changes something in six months?
And on whose bill. Meta regularly adjusts rates, categories and conditions. This is the question that makes the difference between an hourly rate and a monthly amount visible.

How we do it, and what that costs

We are a Meta Tech Provider and build on the official Cloud API. No browser bot imitating a phone, because that is how your number goes off the air sooner or later.

You get a quote up front with a fixed monthly amount covering the integration, the maintenance and the changes. Sometimes there is a start amount as well, and then you get two options: more up front and less per month, or the other way round. The only variable after that is what Meta charges per message.

There is no price list on this site, because every integration differs and a list would be wrong anyway. What is included is above, and it is exactly what an hourly rate does not cover: not the building, the continuing to work when the rules change.

Sources

Meta on messaging limits and quality rating
New accounts start at 250 unique contacts per 24 hours and scale through 2,000, 10,000 and 100,000, provided your templates are received well.
Meta on the customer service window
Non-template messages can only be sent inside an open 24-hour customer service window, which starts when the customer writes to you.
Meta on templates
Every message outside that window is a template Meta reviews first, including the category it falls into.
Meta on support
The channels listed: developer support, the community forum and bug reports for everyone, and a Direct Support ticket for parties with partner status. No chat channel is listed.

Talk it through

Not sure who to hire?

Call us before you commit to anyone. If a freelancer is the better choice for your situation we will say so, and at least you will know which questions to ask.

Book a call

Freelancer or agency? The question that counts is experience with WhatsApp

What a freelancer does well

What goes wrong when nobody has done it before

Business verification is not arranged

Templates get rejected or land in the wrong category

Your number stays stuck at its starting limit

The 24-hour window is not in the flow

What experience actually looks like

Verification is step one or two, not step ten

The messaging model drives the design, not the other way round

The plan has time in it for what routinely goes wrong

It starts small and scales after that

There is a line to Meta itself

And when WhatsApp is only a small part of your project

Six questions to ask any builder

What do you watch out for in a WhatsApp Business implementation?

Have you taken a WhatsApp number live before, and what went wrong?

When do we arrange business verification?

Do you build on the official Cloud API?

How do I see whether a message arrived and was read?

Who adjusts it when Meta changes something in six months?

How we do it, and what that costs

Further reading

Sources

Not sure who to hire?

Freelancer or agency? The question that counts is experience with WhatsApp

What a freelancer does well

What goes wrong when nobody has done it before

Business verification is not arranged

Templates get rejected or land in the wrong category

Your number stays stuck at its starting limit

The 24-hour window is not in the flow

What experience actually looks like

Verification is step one or two, not step ten

The messaging model drives the design, not the other way round

The plan has time in it for what routinely goes wrong

It starts small and scales after that

There is a line to Meta itself

And when WhatsApp is only a small part of your project

Six questions to ask any builder

What do you watch out for in a WhatsApp Business implementation?

Have you taken a WhatsApp number live before, and what went wrong?

When do we arrange business verification?

Do you build on the official Cloud API?

How do I see whether a message arrived and was read?

Who adjusts it when Meta changes something in six months?

How we do it, and what that costs

Further reading

Sources

Not sure who to hire?