Neem fixes the big systems. And the tiny pictures.

A bottle of fabric conditioner has two lives. In one, it is inventory: something to count, forecast and dispatch. In the other, it is a small picture on a phone, competing for a shopper’s impatient glance. Neem works in both worlds. That is an unusual combination for a technology consultancy, and a useful way to understand what this one sells.

The UK business builds software, organises data, supplies specialists and designs digital retail content. Its work reaches from enterprise systems to the particulars of a product label. Read its project descriptions together and a pattern emerges: information exists, but the person who needs it cannot get it quickly enough, understand it easily enough or act on it reliably enough.

For a prospective customer, that puts Neem somewhere between a software consultancy, a digital-commerce agency and a provider of delivery teams. The interesting part is where those jobs overlap. A handsome interface still needs accurate data. A working database still needs a useful interface. A brand’s expensive packaging still has to explain itself at thumbnail size.

First, there was only one Ronald

Neem’s origin story begins with founder and CEO Ronald Tweedie arriving from South Africa with £500. The company recounts that an introduction to a Unilever team led to work improving efficiency and making savings. More demand followed. The immediate constraint was wonderfully unglamorous: the developer had only one pair of hands.

“However, there was a problem; there was only one Ronald.”

Neem’s account of its beginnings

Hiring turned an individual’s capacity into a business. Neem Consulting Limited was incorporated in January 2009. Today the company describes a global team of more than 200 people across 14 countries. Those are its own team figures; the story is about a distributed delivery organisation, with the coordination demands that brings.

Five billion lines, one practical question

At Unilever, the question was how to see inventory across a sprawling supply chain. Neem’s published account describes scattered systems and slow access to their contents. Its response was direct extraction from SAP tables, bypassing conventional tools such as BODS and combining stock, planning, supply and production data. Neem says the approach produced results in days where vendor-led processes had taken months.

The reported workload is considerable: 5.5 billion lines of data processed monthly, with 500 integrations and 1,900 tables and views. These are supplier-reported operating figures. Their significance is less the size of the number than the change in visibility: managers gained a common picture of inventory. A data project earns its keep when that picture helps somebody make a decision.

A separate dispatch project makes the work easier to picture. Neem built a .NET web application across five Unilever factories. Managers entered weekly production forecasts; the system tracked dispatches and displayed estimates against actual movements. The company reports more than 23,000 pallets processed weekly. The old difficulty was basic visibility: production and dispatch were hard to reconcile, contributing to excess stock in some situations and shortages in others.

There is a practical lesson here for a less enormous organisation. Put the forecast beside what actually happened. Make the discrepancy visible to whoever can change the next decision. Buying another dashboard is only useful if the organisation has agreed what goes into it and who will respond when the numbers disagree.

The supermarket shrank. The label didn’t.

The same concern with usable information runs through Neem’s mobile-ready hero image work. A hero image is the principal product visual a shopper encounters. It needs to communicate the brand, the kind of product, the variant and the quantity. Those details can be perfectly legible on a physical pack and become a decorative blur after the image shrinks onto a phone.

This is a design constraint with commercial consequences. A shopper comparing two near-identical bottles needs to spot the difference. Making that person enlarge an image, read a title and return to the results creates work. Neem’s approach gives the buying information a clearer hierarchy. The creative task becomes deciding what deserves those scarce pixels.

For SodaStream, Neem describes desktop-oriented assets struggling in mobile retail settings. It redesigned product imagery, prioritised products and search opportunities, and created reusable layouts for Amazon Brand Stores. The asset library supported more than 40 products. Reuse mattered because local teams needed consistent material across markets, without rebuilding each storefront from scratch.

Neem reports double-digit sales growth across US categories after the work. That is a case-study claim rather than a controlled finding that isolates imagery from every other influence on sales. The practical intervention is nevertheless clear: improve what shoppers can understand, then give the organisation a repeatable way to publish it. A single attractive image cannot solve an inconsistent global content process.

A Rhino with an eye for small print

Rhino packages part of that expertise into a web-based testing tool. It examines text contrast and visual clarity in commerce images, using several contrast methods and Cambridge visual-clarity principles. Bulk testing and API connections are designed to put checking into content-production workflows. A team with a large catalogue can inspect assets before publication instead of relying entirely on individual visual judgement.

The distinction between being noticed and being understood is central to Neem’s recent thinking. In an August 2026 article, the company examines how AI can evaluate text within images. Attention alone does not tell a brand whether someone can decipher the product’s important details. That makes readability a useful additional quality check, especially when content production is being automated.

AI does the extraction. People still check.

Another Unilever engagement began with the tedious work of pulling product claims from material in different markets, translating them and placing them into spreadsheets. The difficulty was language and context: similar claims could be expressed in different ways. Neem’s case study says conventional automation struggled with that variability.

Neem developed a proof of concept before formal engagement, then built a web application with configurable extraction rules, OpenAI integration and CSV import and export. The prototype supplied something concrete to evaluate. Rather than infer a dramatic executive conversion, the documented sequence shows how a working demonstration made the proposed approach inspectable.

The company reports accuracy of 80 to 90 percent and retains manual validation. That boundary matters. A workflow that helps someone prepare and review claims has different requirements from one that publishes them unattended. The copyable idea is to select a repetitive task, show the output early and keep a review step where errors affect the business.

Sometimes the deliverable is the team

Neem’s resourcing operation supplies programme managers, architects, engineers, analysts and other specialists. Its stated selection criteria include communication and cultural fit, alongside technical capability. It describes continuing account management and feedback after deployment. That makes its people-centred culture part of the delivery proposition: the consultant has to work inside somebody else’s organisation.

At MaagTechnic, part of ERIKS, Neem acted on the client side of an SAP programme. The assignment involved governance, financial control, dependencies and oversight of a large systems integrator. Here, the consultancy’s role was to keep technical delivery connected to operational priorities. A buyer can need experienced representation even when it already has a company doing the implementation.

Its development work also extends to smaller ventures. For Ontu, Neem created a brand and two mobile applications, one for drivers and one for roadside professionals. The intended improvement was a structured alternative to WhatsApp groups and phone calls. Vehicle information, location and two distinct user journeys shaped the build. The example shows how design and engineering meet in a service people must use under pressure.

That breadth gives buyers several ways into the company. Its development offer covers websites, web applications, custom enterprise software and supply-chain technology. Its data practice describes work from designing data foundations to embedding analytics into everyday processes. A client can therefore bring a particular application problem or a broader need to connect systems and people. The published offer is wide; the case studies help make it legible.

In market terms, the alternatives depend on the assignment. An internal engineering team might handle a software build; a retail-content agency might redesign imagery; a systems integrator might implement enterprise software. Neem’s combination gives a buyer the option of joining those activities within one engagement. The sensible test is whether the specific team understands the task and can demonstrate relevant work. Breadth on a website is an invitation to ask better questions about delivery.

The rate card brings things back to earth

Neem’s business is sold through projects, consultancy, specialist capacity and support. Its G-Cloud 14 listing quotes £350 to £1,400 “a user a day” for Software Development & Consultancy. That is a public framework range, not the price of the Unilever projects or a Rhino subscription. Scope, staffing, duration and support turn a daily rate into an engagement budget.

For illustration, 20 chargeable days at those endpoints produce £7,000 to £28,000. This arithmetic is a budgeting example, not a Neem quotation; it excludes additional charges. The same listing describes ongoing support and testing, while the company’s public-sector offer includes service transition and integration. Buyers are choosing a delivery relationship as well as a build.

The conditions for success are fairly concrete. Neem’s published service agreement asks the buyer to provide decision-makers, subject expertise, access and necessary licences. Fast external teams still depend on internal cooperation. Similarly, clearer retail imagery cannot replenish missing stock, and an automated extraction tool needs somebody to judge its mistakes. Before commissioning work, identify the blocked decision, the responsible owner and a result that can be checked. Neem’s most useful examples begin there.