Performance profiling engagement

Flagship service · typically 8–12 business days

For engineering leads running Django, FastAPI, Flask, or batch Python who need a defensible answer to “why did this get slow?” before scaling infrastructure.

Engineer working through performance notes

Result you should expect

A ranked list of hotspots tied to real call stacks, at least one merged improvement in your repository (or a ready-to-merge branch if your process requires it), and a short recording walking your team through the before/after profiles.

Who provides the work

Senior consultant at AeroTensor—usually the person who joins your stand-up and stays through the verification run. No offshore handoff mid-engagement.

What is included

What is excluded

Process and timeline

  1. Day 1–2: Access, reproduction, baseline metrics agreed in writing.
  2. Day 3–6: Instrumentation and daily async updates.
  3. Day 7–9: Patches, review with your team, adjust for style and release rules.
  4. Day 10+: Verification and documentation; optional on-site day at 14 Adderley Street if you prefer whiteboard review.

Location and delivery

Remote by default across South African time zones; hybrid with Cape Town on-site days when you want the profiling review in person. We can travel to Johannesburg or Durban with travel billed at cost.

Preparation from your side

Read-only repo access, a contact who can approve short profiling windows in staging, and one person who knows the deployment topology. NDA available on request.

Pricing basis

Fixed fee quoted after the scope call; most engagements fall in the range listed on our Rates page. A 40% deposit holds the calendar slot.

Next step

Request a scope call and select “Performance profiling engagement” in the form.

See how we run profiling week-by-week