Eight client stories with the metrics procurement asks for first
Reviewed by Javier Uanini, CEO and delivery lead, Siblings Software.
If you opened this page from an RFP attachment, you probably need one comparable outcome in your industry—not a logo wall. This hub indexes eight nearshore engagements we can name publicly: fintech payment rails, enterprise Go platform work, smart-city IoT, B2B marketplaces, and multi-year staff augmentation. Each card links to a full story; this page tells you which story to open first and which engagement model it actually reflects.
We publish metrics here that used to stay in slide decks—merchant counts, deployment frequency, fuel savings, onboarding time deltas—because procurement teams in 2026 expect structured proof per contract shape, not generic “we build great software” copy. When you already know you need a managed squad or a single senior seat, jump to the matching dedicated team or staff augmentation page; come back here when you need evidence that the model worked under real compliance and timezone constraints.
What these stories prove (and what they deliberately omit)
A case study hub is not a substitute for vetting detail on a hire page. It exists so you can answer “have you done this before?” without scheduling a call. Across the eight published stories below, three patterns repeat: regulated data paths (PCI-aligned gateways, encrypted collaboration, enterprise observability), nearshore overlap with US hours from Córdoba and broader Argentina/LATAM talent, and contracts that lasted long enough to measure—not three-month pilots that never reached production traffic.
Portfolio scale (public numbers)
- 3,000+ merchants on Sur Technology payment gateway
- $160M processed in a twelve-month window
- 8 senior Go engineers embedded with NetApp platform teams
- 50K gallons of fuel saved via BinSensors route optimization
Delivery signals buyers ask about
- 3× deployment frequency improvement at HighSide
- 42% faster merchant onboarding at Viking Services
- 6 months from kickoff to Bari B2B platform launch
- 32% lower hire cost vs local recruiting (Pentalog)
What we leave for NDAs
Architecture diagrams with cardholder-data boundaries, exact rate cards, and customer-specific audit artifacts stay off public pages. On a scoping call we share redacted sprint dashboards and—when legal allows—a reference conversation with a tech lead who still owns the account.
For how we measure delivery health internally, see the DORA research program—our governance conversations map to deployment frequency and change-failure framing even when clients do not use those exact terms.
Proof Match Filter: three questions before you open a PDF
Procurement teams waste cycles reading the wrong story—a fixed-scope marketplace case when they are buying staff augmentation seats, or a fintech dashboard write-up when they need enterprise platform SLOs. We use this filter on intake calls; it works on this page too.
- Compliance surface — Does your buyer care about PCI, HIPAA-adjacent handling, municipal IoT data, or enterprise uptime SLOs? Match Sur Technology or Viking for payments, HighSide for secure collaboration, BinSensors for smart-city ops, NetApp for platform engineering.
- Engagement shape — Are you purchasing named engineers (staff aug), a managed squad with shared accountability (dedicated team), or a defined product deliverable (project-based)? The library tags each story so you do not compare unlike contracts.
- Bottleneck to unlink — Time-to-hire, release cadence, merchant scale, or field-route efficiency? Pick the card whose headline metric matches the KPI your CFO actually tracks.
“Buyers who send us three RFP questions upfront get a one-page shortlist instead of eight PDFs. The filter saves a week.”
— Javier Uanini, CEO and delivery lead
Published library — eight stories, each with its own URL
Open the full write-up when the headline metric matches your RFP. Summaries stay short on purpose; depth lives on the linked page so Google and humans get one authoritative URL per client—not ten near-duplicate blocks on a hub.
Staff aug · Platform
NetApp — eight Go engineers for platform engineering
Senior Golang engineers embedded with platform teams building cloud-native services—REST/gRPC, workers, and observability aligned to enterprise SLOs. Compare with our Go staff augmentation and dedicated Go squad pages.
Fixed scope · Fintech
Sur Technology — payment gateway for 3,000 merchants
Full REST payment gateway on .NET, Angular, SQL Server, and Azure—PCI-aware architecture, ACH and QR modules, onboarding cut from ten days to 72 hours. See also API development outsourcing.
Fixed scope · IoT
BinSensors — smart-city waste route optimization
REST API, ingestion jobs, and dispatcher dashboard on Azure—50K gallons of fuel saved, route planning dropped from three hours to 25 minutes. Featured on SmartCitiesWorld.
Fixed scope · B2B
Bari — B2B marketplace in six months
Six-person squad (.NET Core, React, GraphQL)—12 distributors, 230 retailers, platform live in six months with ongoing maintenance. Pairs with project-based delivery.
Staff aug · Security
HighSide — DevOps and Python augmentation
Two-year engagement: CI/CD hardening, encryption service refactors, 3× deployment frequency, zero rollbacks over twelve months. Aligns with agile delivery playbooks.
Fixed scope · Fintech UI
Viking Services — Angular operations dashboard
Angular 15, NgRx, Cypress, Azure DevOps on .NET APIs—42% faster onboarding cycles and reusable design system for phase two. Related: front-end outsourcing.
Staff aug · Data
Pentalog — data engineers and DevOps
European software firm scaled via our talent squad—three data engineers plus DevOps, 32% lower hire cost vs local recruiting, relationship beyond one year. See nearshore hiring.
Staff aug · Cross-border
IT Systems Innova — eight developers across stacks
Java, .NET, mobile, front-end, and UX/UI placements for Uruguay/US projects—50% faster cross-border onboarding via shared knowledge base. Spanish version: casos de éxito.
Match the contract shape before you match the logo
The most common mistake on case-study pages is treating every win as proof that your preferred model works. Staff augmentation stories prove interview pass rates, ceremony fit, and retention—not that we should run your entire roadmap. Fixed-scope stories prove launch metrics and operational KPIs—not that you should hire one engineer tomorrow.
Where to go next
- Need a full capability brief with pricing bands? Start at software development outsourcing or platform engineering.
- Evaluating Argentina overlap and nearshore risk? Read hire nearshore developers alongside the Pentalog and IT Systems stories.
- Building AI features and want delivery proof? Pair this hub with AI development outsourcing—the case cards here skew toward production platforms and regulated data, not demo chatbots.
- Need every URL on the site? Use the complete services map.
Featured depth: NetApp platform engineering staff augmentation
When buyers ask for “someone who has done enterprise platform work at scale,” this is the story we send first—not because it is the newest, but because the proof points map cleanly to SLO-driven platform teams evaluating nearshore Go talent.
Situation
NetApp platform groups needed senior Golang capacity for hybrid data infrastructure—services, workers, and observability that had to meet enterprise SLOs without slowing an in-flight roadmap. Local hiring timelines would have missed release windows.
What we embedded
Eight senior engineers joined existing platform squads under the client’s ceremonies and code-review norms—REST and gRPC services, background workers, metrics and tracing wired to the client’s existing stack.
Why it matters for your RFP
- Proves multi-seat staff aug at senior level—not a single contractor hero story
- Platform SLO context closer to platform engineering buyers than a greenfield app rewrite
- Demonstrates Argentina/LATAM overlap with US platform leadership
OUR STANDARDS
What we will—and will not—publish on a case study page.
We only index stories where we can stand behind the metrics in public: verified transaction volumes, measurable operational deltas, or multi-quarter delivery tenure. If a win is under NDA, we describe the pattern anonymously on a service page instead of inventing a logo row here.
Every engagement in this library ran with shared Definition of Done, peer review, and security onboarding before repository access—whether the contract was one engineer or a six-person product squad. That bar is the same one described on our about us page and in the vetting sections of individual hire URLs.
Frequently Asked Questions
Use the Proof Match Filter above: name your compliance surface (PCI, enterprise SLOs, municipal IoT, or secure collaboration), the engagement shape you are buying (staff augmentation seats, a managed squad, or a fixed-scope build), and the bottleneck you need to unlink (time-to-hire, release cadence, merchant scale, or route efficiency). That usually narrows this library to one or two URLs before you open a PDF.
Yes. This hub publishes stories we are cleared to name publicly. On a scoping call we can walk through redacted architecture diagrams, sprint metrics, and—when your legal team provides an NDA—connect you with a reference from a comparable engagement in fintech, platform engineering, or staff augmentation.
No. Roughly half the library is staff augmentation or hybrid long-running aug (NetApp, HighSide, Pentalog, IT Systems Innova). The rest are fixed-scope or product builds where we owned delivery end to end (Bari, BinSensors, Sur Technology payment gateway, Viking dashboard). Each card tags the model so you do not compare unlike contracts.
Several relationships are multi-year and still active—HighSide and Bari maintenance are ongoing examples. NetApp and Viking reflect 2024–2026 platform and fintech work. We refresh this index when a story gains new metrics worth publishing; individual case URLs carry the deeper timeline.
This hub shows headline outcomes we can stand behind publicly—transaction volume, onboarding time deltas, fuel savings, deployment frequency, and team size. A call adds stack-specific vetting detail, governance cadence, and pricing bands tied to your compliance and overlap requirements.
Often yes, after mutual NDA and a confirmed fit on engagement model. We prefer a tech lead who still maintains the client relationship rather than a generic sales engineer reciting slides.
Service pages explain how we sell and deliver—pricing bands, vetting lanes, and risk mitigations. Case studies prove that model under real constraints. Start on a hire or outsourcing page when you know the contract shape; start here when your CFO or procurement lead asked for comparable outcomes before approving a vendor shortlist.
Clearwater Insight Group — queue-driven expert sourcing with BullMQ workers and a Next.js admin console. Read the case study
Relay Works — internal recruiter platform with PostgreSQL full-text search and Google Drive indexing. Read the case study
Canal Vista Desarrollos — Panama residential sales pipeline with server-side legal guards and optional AI agent. Read the case study
Summit Signal Labs — SEO intelligence platform with Temporal workflows and an eight-step pipeline. Read the case study
AAARBA — ExamenCarrera ECEO OSCE examination system delivered for AAARBA. Read the case study