Invoicing · Tunisia
E-invoicing in Tunisia: 2026 rules for software
Tunisian e-invoicing from the official texts: who must comply since the 2026 Finance Law, TTN's role, penalties, and what your invoicing software must handle.
Agencies · Delivery models
White-label development means a partner studio builds software that your agency delivers under its own brand. It works when four things are written down before the first commit: who owns the code and the accounts, what the end client may see, how the teams communicate, and who runs the software after launch.
ANTASY IT (a.it) is a software studio in Sfax, Tunisia. We build for companies directly, and offer agencies white-label delivery. This guide is the checklist we would want an agency to hold any studio to, including us. It is not legal advice: use it to brief your lawyer, not to replace one.
In white label, the studio delivers finished work under the agency’s brand and carries most of the delivery risk, while the end client sees only the agency. A dedicated team or staff augmentation adds people the agency directs, and a freelancer suits small tasks. The real differences are who manages the work and who answers for it.
The table compares the four models agencies usually weigh, including when another model is the better choice.
| Criterion | White-label project | Dedicated team | Staff augmentation | Freelancer |
|---|---|---|---|---|
| Who manages the work | The studio, against an agreed scope | A lead on the studio side, with your priorities | You, day to day | You |
| Who faces the end client | Your agency | Your agency | Your agency | Usually your agency |
| Usual billing | Fixed scope or milestones | Monthly | Monthly, per person | Hourly or daily |
| Delivery risk | Mostly the studio’s | Shared | Yours | Yours |
| Best when | The scope is clear and you need a finished product | Work flows steadily for months | Your team lacks one skill for a while | A small, well-bounded task |
| Another model is better when | The scope keeps moving: take a dedicated team | Work is irregular: buy projects | Nobody can lead the extra people | The work is long or critical |
Our own offer follows the same logic: white-label projects at a fixed scope or by milestones, and a dedicated team or individual developers by the month. The pricing page explains how each model is quoted.
Ten headings, each worth a sentence or a page: confidentiality, ownership and transfer of the code, credits and branding, accounts and access, deliverables and acceptance, change requests, personal data, support after launch, exit and handover, and payment terms. Write them before the kick-off; adding them after the first invoice is much harder.
These are headings, not clauses. Your lawyer writes the clauses, under the law you choose; the headings make sure nothing important is missing from the brief.
The agency or its client, never the studio by default. Domain, DNS, hosting, CDN and analytics accounts belong to whoever will still own the product in five years, with the studio invited as a user. Code ownership should transfer on payment, with the full repository history, not as a zip file sent at the end.
Takeovers show why. When we take over a site or an application built by someone else, the first question is always the same: who holds the domain, the DNS zone and the hosting account? When the answer is the client, a takeover is a technical task. When it is a former vendor, it becomes a negotiation, and the client waits.
Cloudflare deserves a line of its own. If the DNS zone sits in the studio’s Cloudflare account, the agency depends on the studio for every DNS change, every certificate and every cache purge. Put the zone in the agency’s or the client’s account and invite the studio as a member with the narrowest role that works.
By removing its name from everything the end client can see, not only from the footer. Credits hide in page metadata, PDF and e-mail templates, admin login screens, error pages, staging URLs and sender domains. A search for the studio’s name, domain and e-mail across the code and the rendered pages, before launch, catches most of them.
On our direct projects we do the opposite, openly: the Mohamed Damak et Cie website carries a “Développé par AIT” credit that links to us, and our own product Made in Tunisia shows “Réalisé par” followed by our logo. That is exactly the kind of line a white-label delivery must not contain, and in a real codebase it can sit in more places than the footer:
Through the agency’s channels, at the agency’s rhythm. The studio works in the agency’s chat, tracker and repository, joins client calls only when invited and under the agency’s banner, and writes release notes the agency can forward unchanged. From Tunisia, the working day matches Paris and Berlin in winter and runs one hour behind in summer.
Tunisia has stayed on UTC+1 all year since it abandoned daylight saving time in 2009 (opens in a new tab). Our office hours are Monday to Friday, 9:00 to 18:00 local time, and we work in English and French. For a European agency, that is a shared working day, not an overnight hand-off.
The rhythm we propose to an agency, adapted to its own rituals:
The days matter less than the principle: the agency always knows more than the end client, and never learns news from them.
Decide it before launch, in writing. Either the studio keeps operating the software (hosting, updates, monitoring and backups) under accounts the agency or the client owns, or it hands everything over with a documented package. Both work. What fails is the unspoken middle, where everyone assumes someone else will renew the certificate.
Operating what we build is our default with direct clients, through our DevOps and hosting service. For an agency, the same work can run under the agency’s accounts, or end with a handover. Either way, the handover package below should exist from the first release, not be assembled in a hurry at the end.
Six are worth planning for: credits left in templates, accounts opened in the studio’s name, staging sites indexed by search engines, e-mails sent from the studio’s domain, licences bought by the studio, and support after launch that nobody priced. Each takes minutes to prevent at kick-off and days to untangle once the end client notices.
noindex ends up in search results, sometimes under the studio’s domain. Our direct clients’ apps can run on our own subdomains when they choose it; in white label, staging belongs on the agency’s domain, behind authentication.If you are comparing partners, our page on nearshore development in Tunisia covers time zones, languages and how to check a studio’s production work. The process page shows how a project runs from discovery to operations, the agencies hub lists every way we work with agencies, and the glossary defines the terms used here.
Where this applies
FAQ
Start with a small, real piece of work with a clear scope: a module, a page with a form, or a round of fixes on an existing app. Judge the code delivered in your repository, the questions asked before starting, the release notes and how surprises are reported, not only whether the deadline was met.
Yes, if the agreement transfers ownership of the code and requires a handover package: repository with history, documentation, environment variables and infrastructure notes. Without those two clauses, the code may exist yet be impossible to run without the studio. Write them before the project starts, not when it ends.
Only when the agency decides it, and under the agency’s banner. Some agencies invite the studio’s lead to technical meetings with an agency e-mail address; others keep every exchange in-house. Either works, provided the rule is written down and the studio never contacts the end client on its own initiative.
Sources
External facts in this guide come from these documents. Examples from our projects are first-hand.
Keep reading
Invoicing · Tunisia
Tunisian e-invoicing from the official texts: who must comply since the 2026 Finance Law, TTN's role, penalties, and what your invoicing software must handle.
ERP · Decision guide
Custom ERP or Odoo? An honest decision grid for SMEs: process fit, recurring costs, Tunisian tax rules, code ownership, and when Odoo is the better choice.
Engineering · DevOps
How we run Next.js 16 and Strapi 5 on our own server: PostgreSQL, pm2, nginx, Cloudflare, six Strapi traps, and the cache header that kept old pages live.
Tell us about the project and how your agency works; we adapt to your tools and your rhythm.