Case · Defense tech

AIDrones UA: a company website in three languages.

AIDrones UA manufactures robotic and unmanned systems and was heading into international negotiations. They needed a site that explains who they are, quickly and credibly, in three languages, and there were seventy-two hours to do everything: design, build, content and imagery. Webflow, Ukrainian, English and German, AI imagery labelled.

  • Defense tech
  • Robotics
  • Webflow
  • Content
  • AI imagery
  • UK · EN · DE
  • Ukraine
aidrones.com.uaAIDrones UA website preview
3 languages

Ukrainian, English and German versions, switched from the header. checked on the live site · Sep 2026

Built on Webflow

Products, news and press as collections the client edits. checked on the live site · Sep 2026

Content and imagery included

We wrote the texts and made the visuals with AI, labelled, because there was no time for a shoot.

The project

Task, approach and delivery

The task

AIDrones UA manufactures robotic and unmanned systems and was heading into international negotiations. The people who mattered were partners, investors and procurement outside Ukraine, and they needed a site that explains who the company is, quickly and credibly.

There were seventy-two hours to do everything: design, development, every block, the content and the imagery.

The approach

We designed and built the full site in three days and delivered it in three languages from day one. The structure follows the way a serious buyer reads: what the systems do, where they are used, what they are built from, then a short path to a named person.

The tone is deliberately restrained. Where there were no photographs, the visuals were made with AI and labelled; the texts were written by us from the company’s materials.

What we delivered

The client walked into negotiations with a live, trilingual presentation site on Webflow, designed, built, filled and illustrated end to end in three days. Domain and hosting in the client’s name.

A multilingual company presentation under a fixed deadline

The AIDrones UA project had an unusually compressed schedule: the agency’s project records describe a three-day website delivery before international meetings. The useful lesson is how design, content and language versions can be organised around a specific presentation need. That timeline belongs to this case; it is not a promise that any website of similar appearance can be delivered in seventy-two hours.

A readable hierarchy on a dark first screen

The saved project capture shows a dark opening with a large white heading and two clearly separated actions. The bright yellow-green button introduces contact, while the white secondary action leads to more information. A compact media card occupies the lower right. The background supports the technical character, but the heading and actions carry the practical meaning. Their contrast lets a visitor identify the next step without depending on the background image.

The navigation is held in a rounded dark bar, and the active item is a light capsule. Bracket-like details appear in the labels and heading. Those repeated graphic decisions create a coherent interface without requiring many different colours or decorative elements. For a company presentation under time pressure, a limited visual vocabulary is useful: the designer can apply it consistently to additional sections rather than invent a new treatment for each screen.

The deadline changes the preparation, not the facts

The recorded scope included design, Webflow implementation, text and visual materials. Preparing all of those together can reduce the number of handoffs, but it also makes source material especially important. The agency can organise a company’s information; it cannot establish technical claims merely by writing them fluently. The published presentation needs to be based on material the company is able to approve.

For a similarly urgent corporate website, we would identify the minimum complete story before starting detailed layouts. It should explain who the company is, provide the approved overview relevant to the meeting and offer a reliable contact route. Optional editorial sections can be separated from that essential scope. This is a planning recommendation for a comparable project, not a reconstruction of every hour spent on AIDrones.

A deadline also requires one clear approval route. If several people provide incompatible wording at the last moment, speed in layout does not solve the content problem. The brief should name who approves the company description, translations and imagery. Decisions that cannot be verified in time should not be converted into confident claims just to fill a block. A concise approved statement is more useful than an elaborate statement whose meaning nobody owns.

Three kinds of material, three different roles

Company information
This identifies the organisation and establishes the context of the presentation. A comparable website should use approved names, descriptions and contact details. The design can make them easier to read and find; it cannot substitute for the company’s own confirmation. The same discipline should apply in every language version, including the small labels around a contact action.
Illustrative material
The project records include AI-created imagery where photography was unavailable. An illustration can support a visual direction, but it should not be presented as evidence of a real event, manufactured item or verified capability. In a similar commission, generated and documentary materials need distinct roles, with the client approving both the depiction and how it is described.
Press references
The gallery includes a press page, which gives external coverage a separate place in the structure. A reference should identify the actual publication and provide context. It does not automatically become an independent endorsement of every statement on the company website. The value of this page is that a reader can distinguish the company’s own presentation from material published elsewhere.

Keeping the language versions aligned

  1. Approve the core meaning

    Ukrainian, English and German versions are recorded in the project. A similar workflow should first settle the meaning of names, headings and the company description, so translations do not begin from several competing drafts. This gives the language work a stable foundation even when the delivery schedule is short.

  2. Review terms in context

    Short navigation labels, explanatory paragraphs and contact messages require different levels of detail. A translated phrase must fit its role in the interface, not simply fit a dictionary equivalent. For a comparable build, we would review each language on its actual page, where the surrounding headings and actions make the intended meaning clearer.

  3. Check the visitor’s route

    The review should include opening a language version directly, moving through its content and reaching the correct contact action. Switching languages should preserve a recognisable company identity. This is a website acceptance task; it does not mean that HeadPills verifies the client’s engineering products or the outcome of its international meetings.

A presentation that can be maintained after the meeting

The project materials identify Webflow collections for the client’s content, including news and press. That matters because a website created for a near-term event may remain the company’s public presentation long afterwards. The launch deadline should not leave a page that only its original designer can update. The editing model needs to distinguish routine content work from changes to layout or functionality.

For a comparable handover, we would ask the client to update one news item and one approved image within the prepared structure. The exercise reveals whether headings, dates and captions have obvious places and whether the team understands the difference between replacing content and altering a component. It also makes the future owner of each section explicit. Access to an editor is useful, but it is not a complete publishing process on its own.

What this case can tell you about an urgent website

A similar brief should begin with the meeting date, the required language versions, approved company material and a named person for decisions. The agency also needs to know which existing assets can be published and which still need preparation. These inputs determine whether the initial scope is realistic. The number of languages alone does not predict the schedule, because unresolved content can take longer than building the page that contains it.

This portfolio case documents a Webflow presentation site and content work completed within the schedule recorded by the agency. It does not report the outcome of the client’s negotiations, investment raised or sales generated. The relevant design result is a coherent company presentation that combines an explicit hierarchy, aligned language versions and a route to contact. For a new commission, we would agree its own scope and schedule from the available materials rather than reuse the exceptional three-day figure as a universal offer.

What the site does

Project features

  • Reads like a serious buyer

    What the systems do, where they are used, what they are built from, then a named person.

  • Three languages

    Ukrainian, English and German, switched from the header.

  • Products as pages

    Each system with its purpose and specifications.

  • Press and news

    What media wrote, kept current by the client.

  • AI imagery, labelled

    Visuals made where photographs did not exist.

  • Edited by the client

    Collections in Webflow for products and news.

“We needed a site that explains complex technology to partners and buyers without a single photo shoot. HeadPills wrote the content, made the visuals with AI and built the site so it reads clearly on any device. Serious topic, clear presentation.”
AIDrones UA · Defense robotics, Ukraine · approved by the client

Questions

About AIDrones UA

Which languages does the AIDrones UA site have?

Ukrainian, English and German, as checked on the live site in September 2026.

How long did the AIDrones UA site take?

The agency’s project records specify a three-day delivery before international meetings. This was a case-specific schedule, not a standard promise for new projects.

Were the AIDrones UA visuals made with AI?

Where there were no photographs, yes, and they are labelled as such. The texts were written by HeadPills from the company’s own materials.

Start a similar project.

Tell us what your site has to do. A short call, then a fixed price in writing.