Goat ScaleBook a 40-minute call
Services

Six things we do, and the numbers they moved.

We do not sell strategy separately from the build. The people who write the plan are the people who ship it, and the plan names one number, one date and one method before anyone opens an editor.

4–6
people on a pod, named before you sign
12 weeks
minimum term, then month to month

Legacy migration

Your core runs on something written before 2005, the people who wrote it have retired, and every change takes a quarter.

What you get
  • A read of the existing system that names what it actually does, not what the documentation says
  • A strangler path that keeps the old system serving while pieces move
  • The new services, in production, with the old ones switched off
  • Runbooks and on-call rotation handed to your team before we leave
Typical length 16 to 24 weeksPod of 5: two backend, one platform, one delivery lead, one part-time architect
Where it was used
Order to dispatch · Vetri Logistics19 weeks
41 hoursbefore
9 hoursafter

Measured 14 March 2026. Median across 8,412 consignments, Feb–Mar 2026, against an August 2025 baseline drawn from the same yards.

Their own six-engineer platform team runs the dispatch service and carries the pager.

ERP replacement

The books are closed out of spreadsheets, three departments keep private copies of the truth, and nobody trusts the stock figure.

What you get
  • A chart of accounts and item master your finance team agrees to before any software is chosen
  • Migration of open transactions with a reconciliation you can show an auditor
  • Parallel run for two closes, with variances explained line by line
  • Training run by your own super-users, not by us
Typical length 20 to 28 weeksPod of 6: two functional, two engineering, one data, one delivery lead
Where it was used
Month-end close · Anaimalai Textiles22 weeks
11 daysbefore
3 daysafter

Measured 6 April 2026. Working days from period lock to signed management accounts, averaged over three consecutive closes.

Finance runs the close themselves. We are not in the room for it.

Data platform

Every question takes a week and comes back with two different answers depending on who ran it.

What you get
  • Ingestion from the systems you actually have, including the ones held together with CSV exports
  • A modelled layer with tests, so a broken number fails loudly instead of quietly
  • The three or four decisions the platform exists to serve, wired end to end
  • Your analysts trained to extend the models themselves
Typical length 14 to 24 weeksPod of 4: two data engineers, one analytics engineer, one delivery lead
Where it was used
Stock-outs on top 200 SKUs · Sembian Retail24 weeks
14.2%before
4.6%after

Measured 30 April 2026. Share of store-days with zero shelf stock, all 62 stores, six-week window against the same window a year earlier.

Their analytics team maintains the forecast models and the replenishment rules.

Checkout and payments

You are losing money between the cart and the confirmation screen and cannot say exactly where.

What you get
  • A measured funnel before we change anything, so the claim at the end is defensible
  • A rebuilt checkout with the failure paths designed, not left to chance
  • Gateway routing and retries that survive a bank going down on a Friday evening
  • Reconciliation between gateway, ledger and bank that runs daily without a human
Typical length 8 to 12 weeksPod of 4: two full-stack, one payments specialist, one delivery lead
Where it was used
Checkout completion · Kovai Kitchen9 weeks
58%before
81%after

Measured 2 February 2026. Sessions reaching payment success over sessions entering checkout, 30-day window, n = 214,000.

Two of their engineers ship checkout changes without us.

AI in operations

A model demo impressed everyone in the room and then nothing reached the people doing the work.

What you get
  • The narrow task it should do, chosen by watching the work, not by workshop
  • A review lane where a person can disagree with the model and that disagreement is recorded
  • Evaluation on your own historical cases with the error rate written down
  • A kill switch and a fallback that your operations lead can use without calling us
Typical length 12 to 18 weeksPod of 5: two ML, one backend, one domain analyst, one delivery lead
Where it was used
Discharge summary turnaround · Meenakshi Health16 weeks
6.2 hoursbefore
47 minutesafter

Measured 21 January 2026. Time from discharge order to signed summary, median of 11,900 discharges across four sites.

Their clinical systems team owns the drafting model and its review queue.

Engineering team setup

You have decided to build in-house and the first six hires will decide whether that works.

What you get
  • Hiring loop, scorecards and a take-home your candidates will actually finish
  • The first codebase, CI and deploy path, built to be handed over
  • Pairing with every new hire for their first month
  • A written exit date agreed at the start
Typical length 12 to 16 weeksPod of 3 to 4, shrinking each month by design
Where it was used
New engineer to first production deploy · Ashvin Motors12 weeks
34 daysbefore
4 daysafter

Measured 18 June 2026. Calendar days from start date to a merged change running in production, for the 11 engineers hired after March 2026.

The team hires, onboards and reviews without us. We left in June.

What we turn down

We say no to about a third of the work that reaches us.

Usually because the thing that is broken is a decision, an incentive or a process, and no system we build would survive contact with it.

  • Staff augmentationWe do not place individual engineers into your team by the month. A pod or nothing.
  • Fixed-scope RFPsIf the scope is already written and cannot change after we look at the system, we are the wrong firm.
  • Pilots with no baselineIf nobody will agree what to measure beforehand, the result cannot be argued either way.
  • Rescues without authorityWe will not take on a failing programme unless we can change what is being built, not just how fast.
  • Anything we cannot hand overIf your side has nobody to hand the work to, we will say so on the first call.

Start with the two-week diagnostic. ₹6.5L, fixed, and the write-up is yours either way.

Book a 40-minute callRead a full case study