For agencies
Drupal delivery partner for agencies
Where we fit
When agencies bring us in
-
A client asked for Drupal
Your client needs Drupal and there is no Drupal capability in-house, with no appetite for a hiring or retraining cycle to build one for a single account.
-
More Drupal work than the team can ship
The pipeline holds more than the current team can deliver against deadlines that are already promised.
-
A pitch or tender needs a named technical partner
A proposal needs a technical partner, a methodology and evidence of relevant work attached before it goes out. We can size the technical scope while the pitch is still open.
-
An inherited platform in unknown condition
You won an account, or took over from a previous provider, and nobody can yet say what state the platform is in.
-
A previous developer left it half-finished
The last supplier ended badly and it is your reputation on the line the second time around.
Terms
How the partnership runs
-
White-label or co-branded, decided per project
White-label means you front the client end to end: we work to your brief, deliver into your process, and your client sees your team. Co-branded means we join client calls and technical reviews as your technical partner, named and introduced, which is usually what happens when the client has its own IT people who want someone to talk architecture with. The same agency can keep us invisible on one account and introduce us on the next.
-
Your client stays yours
We sign an NDA before platform details are exchanged. We work to your brief and do not approach your client for work outside your scope. If you want that written into the partnership agreement rather than left as a promise on a web page, we will sign it.
-
We invoice you, not your client
Billing runs to the agency, with a report itemised by project so you can reconcile it against what you bill your client.
-
Nothing gets published without your permission
No engagement becomes a case study, a logo or a talk slide without written agreement from whoever owns the client relationship.
-
You talk to the engineers
Ukrainix is a boutique team. There is no account manager relaying messages: you reach the people writing the code, and the same people stay on your account across years.
Scope
What we take on
The scope you can draw on, whole or in part.
-
Migrations and upgrades to Drupal 11
We moved 1.5M+ entities from Drupal 7 to 9 for a national newspaper with SEO preserved through deliberate redirects and metadata.
-
Long-term support and maintenance
Security patches on a schedule, core and module updates before an end-of-life date forces a panic, performance and uptime watched. Including Drupal 7 sites still in production.
-
Inherited platform takeover
A scoped audit first: what you are holding, what it costs to fix, and in which order, before you commit your client to a plan.
-
Integrations
Third-party APIs into content-managed sites, for example the LibCal integration we built for Tulane University Libraries, which pulls live room and event schedules into the site.
-
Commerce and large catalogues
We currently support a Drupal 7 marketplace with over 2.4 million products, more than 50 custom modules, supplier feed imports and exports, and faceted search.
-
Accessibility and multilingual work
WCAG 2.1 AA as a baseline on new work, and multilingual Drupal including full rebuilds during migration.
Detail on each: Drupal audit Drupal modernization & migration Drupal support & ongoing development Drupal architecture & complex builds Integrations & APIs Drupal Commerce & marketplaces Headless & decoupled Drupal DevOps support Drupal 10 → 11 readiness review
Commercials
Commercial models
-
Hourly
Time and materials for support, maintenance and enhancement work, billed against the hours actually logged, with an itemised report.
-
Monthly retainer
A fixed number of hours per month when you want a predictable line in your own budget.
-
Fixed price after audit
For upgrades and migrations we run a compatibility audit first, then quote a firm fixed price, so the number is accurate rather than a guess.
Availability
How we respond
We reply within one business day. Working hours are weekday, UA / EU time. We do not claim round-the-clock availability, because a boutique team cannot hold that honestly. What we do hold: the same engineers stay on your account, urgent issues are looked at the day they arrive, and every change request is estimated and approved before anything is built.
Questions
What agencies ask first
No. The end client belongs to the agency. We work to your brief and do not pursue your client for work outside your scope. We will put that in the partnership agreement if you want it in writing.
Yours, unless you decide otherwise. Repositories, boards, chat channels and documents carry whichever identity the model calls for, agreed at kick-off rather than improvised mid-project.
Every change request is estimated in hours and waits for your written approval before work starts. Nothing outside the agreed scope is built without it.
You do. Code, configuration and documentation live in a version-controlled repository throughout, so the platform can be handed to anyone at any point.
Yes, and we would suggest it. One contained task tells you more about how we work than any call. Most partnerships here started that way.
Proof
Platforms we run for other people
No commitment
Start with one task, not a contract
-
A call, not a pitch
Thirty minutes with an engineer about your pipeline, the platform in question and how you run delivery. No deck, and no discovery invoice.
-
One contained task
Pick something small and real: a bug, an upgrade check, a scoped feature. You see the code, the estimate discipline and the communication before anything of yours depends on us.
-
Then the account
If that went the way you want, we take on the account and the same engineers stay on it. Most partnerships here started exactly that way.
Send us the brief
Tell us the platform, the constraints and the deadline. A senior engineer reads it and comes back with the questions that decide scope, not an autoresponder. If you would rather test than talk, send one contained task instead.
- Reply within one business day, weekday hours UA / EU.
- 30-minute discovery call when it is useful.
- Scope written around deliverables, risks, and ownership.