Buenos Aires
A letter from a small WordPress studio.
Hello. We're Tamandua — two engineers in Buenos Aires, building WordPress since 2010. This page is the whole pitch: what we do, how we work, and where to write if you want to work together.
What we build
Three things, mostly.
Custom themes, built from scratch to fit the brand, and written so the next developer can open the code and get straight to work.
Plugins that do one job well. When your workflow needs something WordPress doesn't do out of the box, we build that piece, document it, and wire it into what you already run.
And when the project calls for it, whole platforms — architecture, build, launch, support — with performance, SEO and accessibility built in from the first commit.
By now you may be thinking this all sounds a bit… small.
It isn't. Keep scrolling.
…and then we make it look this simple again. That's the whole point.
A few we've shipped
Recent first, a line each. Names where the client's happy to be named, shapes where they're not.
-
Rebuilt a Uruguayan daily on WordPress: an editorial redesign, a custom subscriptions system, and thousands of archived articles migrated behind clean 301s.
-
A medical e-commerce platform
Traced seventeen-second carts and checkouts on a WooCommerce store down to its external calls — an ERP, FedEx, and a serverless license check — and caught a bug quietly serving every customer default prices instead of their negotiated ones.
-
Took a nationwide branded-merch store from a no-code prototype to a real WordPress build — the full catalog plus a B2B quote flow with multi-address shipping and artwork upload.
-
A pharmacy group near Manchester
Several pharmacies running on one shared codebase — each branch's site stood up as a controlled clone of the last, clinical-service pages and booking swapped per location, every page SEO-verified before it deploys.
How we work
We listen before we quote. The first call is about your business and what's getting in the way — then a proposal in plain language: what we'll build, how long it takes, what it costs. If a smaller project would serve you better, we'll say so.
While we build, you watch: work lands on a staging site every few days, and you talk straight to the two people writing the code. No account manager forwarding your emails, no "delivery lead" who's never opened the repo, no flights on your invoice for what could've been a Google Meet.
That overhead gets paid twice — once by you, once by whoever's building your site, in cut corners and 2am shipping. Two of us, no middle layer, so nobody pays that bill. At launch you get documentation, training, and a clean handover; if you ever take the work in-house, it goes with you.
The AI part
We use AI all day, and we've gotten good at it. Every commit gets reviewed by the two of us plus an AI reviewer in the pipeline — roughly a third engineer on call. The code is still ours; we just ship it about three times faster, with fewer bugs reaching production.
If AI tooling makes you uneasy, we're probably not your studio — and we'd rather say that up front.
What it costs
We're in Argentina: senior work at a lower cost of living, same quality. We quote a fixed price per project after the first conversation, and it doesn't move.
Tamandua Software
Buenos Aires ·
P.S. This site is a single HTML file, no framework, barely any JavaScript — except for the part where it lost its mind for a moment. You scrolled through that. It's roughly how we build everything: as simple as the job lets us get away with.
Write to us
Tell us what you're trying to build — a line or twenty, both work. We reply within a business day, and if we're not the right fit we'll point you somewhere better. We only take a couple of projects at a time, so write early.