industries we build software for

CodigoDelSur has built software in most industries since 2007, and on its own that is not useful information. Every development company can say it. What is worth reading is where the work has piled up enough that we can name the clients, say what our engineers built and what the client built, and say how long we stayed.

That is what this page is: one row per industry, what we build in it, and the case studies you can open and read. Where a row has its own page, there is a lot more detail behind it.

LET’S DISCUSS YOUR BUSINESS NEEDS TODAY

Where our track record actually is

Seven industries, what we build in each one, and the case studies you can open and read. A client can appear in more than one row, because a drone mapping platform used on farms and on construction sites is genuinely all three.

Industry	What we build there	Case studies
Agriculture and agtech	Drone scouting and flight software, pest management tools for scouts and agronomists, dairy operations platforms, and trading and traceability systems for what happens after the harvest	Milc Group, Bluefin, AgroScout, Skippy Scout, DroneDeploy, Caravela Coffee
Drones, mapping and geospatial	Flight control on the DJI SDK, automated missions, image capture, pre-flight and in-flight safety checks, and flight logs used for compliance, insurance and fleet maintenance	DroneDeploy, AgroScout, Skippy Scout, Ware
Health, dental and wellness	Consumer health and tracking apps, products that talk to a connected device over Bluetooth, and dental and clinical tools	Kindara, Shred, Tooth Magic Memory
Fintech, payments and identity	Payments and travel finance, financial data platforms, and identity and document verification built to run at volume	Acuant, Uplift, StreamWolf
Media, entertainment and streaming	Subscription platforms and paywalls, photo and video products, and audio and content discovery apps	MoviePass, Shutterfly, Earbuds, Seekr, Taste, StreamWolf
Commerce, marketplaces and consumer apps	Ordering and booking flows, two-sided marketplaces where supply and demand are different products, retail and personalisation, and checkout	Grubhub, Shutterfly, Wyndy, Dauber, Vartender, Supreme Golf
Construction, logistics and property	Jobsite capture and mapping, warehouse and fleet operations, field service tools for crews who are not at a desk, and property and facilities platforms	DroneDeploy, Ware, Convex, PacPost, Blue Cimarron, Dauber

Agriculture is the only row with its own page so far, and it is the model for the rest: the products we can name, what our engineers built and what the client built, and how long each engagement ran. The others are being written in the same shape, starting with drones.

Five questions to ask any development partner before you sign

Not only us. These are the five that separate a partner who has done the work from one who has read about it, and each one is either answerable in a sentence or not at all. We answer all five on this site, and where we cannot, we say so.

Name one client in my industry, and the product I can open. A description is not a name. If the answer is "a leading agriculture company" rather than a company you can look up, nothing that comes after it is evidence. It is the fastest question in this list and the one that eliminates the most partners.

What did you build, and what did the client build? The interesting part of a product often belongs to the client: detection models, clinical protocols, hardware, agronomic thresholds. A partner who lets you assume otherwise is expensive to find out about later, and it takes one reference call to check.

How long did that engagement run, and how did it end? Anyone can show a logo. What says the most is how long they stayed and what the ending looked like, because leaving well is the only part of the relationship a supplier has no incentive to plan.

Which of the engineers you are proposing worked on that project, and can I interview them? The work that gets shown and the people who get staffed are not always the same. Ask for the link between the two, and ask to talk to them before anything is signed rather than after.

What happens when someone leaves, and who pays for it? Every engagement loses someone eventually. Get the replacement policy in writing before you need it: how fast, at whose cost, and how many days of overlap you get so that the context does not land back on your team.

Other industries we have shipped in

These do not have a page of their own yet, and in every case the reason is the same: most software is built under an NDA and only some of it can be shown in public. It is a publishing limit rather than an experience one. What follows is what we can show.

Industry	What we build there	Case studies
Education and corporate training	Online course platforms, learning management systems, and training products used inside companies rather than schools	Emeritus
Legal and legal tech	Case and matter management, document automation, and platforms built on top of Salesforce for firms that already run on it	Litify
Travel and hospitality	Booking and itinerary products, guest-facing apps, and the finance and payment layers that sit under a trip	Etch, Uplift
Golf and sports	Tee time search and booking, course and club operations, and player performance apps that read a swing on the phone itself	Supreme Golf

If your product is in one of these and you want references before you talk to us, ask on the first call and we will arrange them directly rather than pointing you at a page that does not exist yet.

What is the same whichever row you are in

The industry changes what the software has to survive. It does not change how we work, and the terms below are the same in every row.

Three ways to engage. Staff augmentation, where engineers join your existing team. A dedicated team, which owns a product or a workstream end to end. Or full-cycle product development, from discovery to store release. Picking the wrong one of the three is the most expensive mistake in this category, and both pages say when their model is the wrong answer.

How a team starts. Five business days from a signed agreement to the engineer's first day is the standard, or as soon as the next business day if the profile is already on our bench. The minimum term is two weeks, one sprint, in every model, and the minimum project size is $10,000, roughly one engineer for one month. If an engineer is not working out we replace them at our cost, with ten business days of overlap that we do not bill.

Hours. Our engineers work 10:00 to 19:00 Uruguay time, which covers the entire US East Coast working day and five to six hours of live overlap with the West Coast. We are in Montevideo, Uruguay, and we work with companies in the United States and the rest of the world.

Ownership. Everything created for you is assigned to you with full title guarantee, including any model trained on your data. We do not reuse one client's data or code on another client's project.

The full list of published work, across every industry on this page, is in the portfolio. There are more answers about how engagements work if that is what you are comparing.

Frequently asked questions

Do you specialize in an industry or work across all of them?

Across all of them, and we would rather say that plainly than claim a focus we do not have. What we do have is a handful of industries where the work has piled up enough to be worth reading about, and this page is that list. Agriculture is the clearest one: products we worked on across more than a decade, from drone scouting to dairy operations to coffee trading, with a page of its own that names the clients and says what we built for each.

My industry is not on this page. Does that mean you cannot help?

No. Since 2007 we have worked with more than 250 clients and the products we built have reached over 300 million users, so the odds are we have shipped something structurally like yours even if the label is different. This page is about what we can prove in public, not about what we can do. Tell us what the product has to do and we will tell you on the first call which parts we have built before and which parts we have not.

Why do so few of these industries have a page of their own?

Because the bar we set ourselves is the first question above: we do not publish an industry page unless we can name the clients in it. Most software work happens under an NDA, and a partner who publishes a long list of industries has usually solved that by writing pages that name nobody. We would rather have one page you can check than seven you cannot, and we are writing the rest as the permissions come through.

Will the engineers on my project know my industry?

Some will and some will not, and it is worth being precise about what that is worth. Domain knowledge matters where the domain reaches into the code: a drone SDK, a dairy operation, a coffee export contract, a payment rail. It matters less than most buyers expect everywhere else. We tell you which of our engineers have worked in your industry, on which named project, and you interview them before anyone starts.

How fast can you actually start?

Five business days from signed agreement to first day is the standard, and if the engineer is already on our bench and your side is ready to receive them, they can start as soon as the next business day. What varies is finding the right person, not starting them: if the profile is on our bench you get CVs one business day after you sign off the role brief, and if the role has to be recruited, first CVs take about five business days. We tell you which of the two you are in on the first call, before you have signed anything, because that is what actually moves your start date.

Tell us what you are building

Tell us what the product has to do and who uses it. On the first call we will tell you which parts we have built before, on which named project, and which parts we have not, and that second list is usually the more useful one. CodigoDelSur has been building software since 2007, from Montevideo, Uruguay, for companies in the United States and the rest of the world.

FIND OUT MORE ABOUT OUR INDUSTRIES