Gerson Correia

Fractional delivery lead for remote software teams of 15–60 engineers

Find out in two weeks why your releases slip, and what to fix first.

I map where work actually waits in your Jira, Azure DevOps or Asana, show you the one bottleneck to fix first, and give you a delivery date as a range you can defend.

Engineer first · 9+ years leading software delivery · +25% delivery capacity across 4 squads, same headcount

Request a 20-minute delivery diagnostic See the Health Check
Portrait of Gerson Correia

Gerson CorreiaFree, on video. Your morning in New York, your afternoon in London.

Release 3.2 · forecast from 12 weeks of throughputIllustrative

Last plan: 30 Oct, moved 3 times

85% likely by 18 Nov50% likely by 14 Nov
5 Nov14 Nov18 Nov26 Nov
Each bar is how often a simulated run finished that day. Dark bars are inside the 85% range.
+25%delivery capacity, same headcount, 4 squads
9+ yearsleading software delivery
25+ projectsgoverned in one portfolio as PMO head
Open sourcestatus automation I built and maintain

Sound familiar?

When deadlines stop meaning anything

  • You give a date, miss it, and play the same game again next quarter.
  • The round closed, the team grew, and output didn't.
  • Estimates get doubled, and dates still slip.
  • Every Friday, two managers rebuild the status report from Slack threads.

What your status work costs

Example values. Change them to your own.

Per year, at 46 working weeks US$33,120 about US$2,760 a month A 2014 Harris Poll found US workers spent 4.6 hours a week preparing for status meetings (source).

What changes

From padded dates to a range you can defend

TodayAfter
You double the estimate and still miss the date.You give a range with a stated confidence, from your own last 12 weeks of data.
Friday afternoon goes to rebuilding the status report.The readout rebuilds itself from Slack and your tracker.
Everyone is busy, and nobody can say where a feature is stuck.You can point to the step where work waits, in days.
Planning is an argument about opinions.Planning starts from throughput everyone can see.

Request a 20-minute delivery diagnostic

How I work with engineers

Fewer meetings, not more

Engineers are right to distrust process people who add ceremonies. I was a developer for five years before I led delivery. I start from the data already in your tracker, cut meetings that don't change a decision, and automate the status work instead of asking people for more updates.

A good fit

  • A remote or hybrid software team of roughly 15–60 engineers
  • At least 3 months of history in Jira, Azure DevOps or Asana
  • A leader who owns delivery dates
  • Dates slipping, or status work eating your managers' week

Not a fit

  • Teams of fewer than about 8 engineers
  • You need someone to write code or own the architecture
  • You want individual developer rankings
  • You are hiring for a full-time role

The method

Flow to Forecast

Four steps from opaque delivery to dates you can plan around. Each step ends with something your team keeps.

  1. 1

    Map the real flow

    Short interviews and your tool history show how work actually moves, including the handoffs nobody documented.

    You getA map of the real workflow, with the waiting time at each step

  2. 2

    Measure

    Cycle time, throughput and work in progress, pulled from 3–6 months of your tracker history.

    You getA baseline and a metrics board your team can read

  3. 3

    Fix the constraint

    Remove the biggest bottleneck first: limit work in progress, redesign the worst handoffs, keep only the meetings that change decisions.

    You getMore work finished with the same people

  4. 4

    Automate and forecast

    AI agents take over status relay and reporting. Dates come from real throughput, as ranges with a stated confidence.

    You getA live executive readout and forecasts your team runs without me

The Health Check covers steps 1 and 2 and a first forecast. Steps 3 and 4 are the Fractional Delivery Lead and Status on Autopilot.

Results

What changed for the teams I led

From my in-house and agency delivery roles, before I went independent. Company names are left out.

Cloud ERP software company4 product squads · development manager

+25%delivery capacity with the same headcount

Challenge
No shared view of flow across four squads. Capacity was argued by opinion, and a core financial module had to ship without disrupting customers.
What I did
Built the company's first Lean metrics board, trained the squads to act on it, and split the module rollout into parallel, MVP-first workstreams.
"He set up several workstreams to deliver the financial epic within a single sprint. The system went live with an entire new module, built MVP-first, without disrupting users."
Senior Software Engineer on the team · translated from Portuguese
Medical education group25+ strategic projects · PMO head

A shorter approval cycle and less rework at approval

Challenge
More than 25 projects competing for approval and capacity. Business cases were often sent back, and directors lacked a current view.
What I did
A maturity scorecard for business cases, an approval process with pre-alignment and sign-off gates, and live dashboards for directors.
Series B AI companySupport, engineering and implementation teams

Status reporting rebuilt from live data instead of retyped

Challenge
The real state of work lived in Slack threads; the tracked state lived in Asana. Someone retyped one into the other every cycle.
What I did
Mapped the cross-team lifecycle with directors and leads, then built an AI agent that moves Slack updates onto the right task. The agent is open source.
"He is a very outstanding professional in the area of project management… excellent communication and proactivity with the team makes him a natural leader."
Tech Director
"Gerson has a strong command of agile practices and is always looking for ways to improve processes and streamline workflows."
Product Manager

Start here

The Delivery Health Check

Know in 10 business days why delivery slips, what to fix first, and when your next milestone will realistically ship.

What you get

  1. A map of your real workflow, request to release, with the waiting time at each step
  2. Baseline metrics from 3–6 months of tracker history: cycle time, throughput, work in progress, work-item age
  3. The top 3 constraints, ranked by the days of waiting they cause
  4. A forecast for one milestone you name: a date range at 50% and 85% confidence
  5. The cost of your manual status work, in hours and dollars
  6. A 30-day action plan with owners
  7. A 60-minute readout for your leadership, recorded
US$4,500fixed price

Founding rate: US$3,000 for the first three clients, in exchange for a named case study.

Low risk: half at the start. The second half only after the readout, and only if it delivered everything listed.

10 business days from read-only access. About 4 hours of your team's time.

Ask whether a Health Check fits

After the Health Check

Fractional Delivery Lead

I run your delivery system part-time, about 8–10 hours a week: cadences, the metrics board, stakeholder reporting and coaching for your leads, then a planned hand-off.

From US$5,000 a month

After the Health Check

Status on Autopilot

Your real process mapped, status updates flowing from Slack into Asana or Jira, and a live executive readout instead of a weekly document.

From US$6,000

Scrum and Kanban training for squads, built around your own board, is quoted per session.

Portrait of Gerson Correia

About

An engineer who became a delivery leader

I started as a C# developer in 2012, so I talk with engineers as a peer, not as someone collecting status. Since 2017 I've led delivery as Scrum Master, project manager, development manager and PMO head, in Brazil and for remote clients in the US, Europe and LATAM.

Since October 2026 I work independently. I make the real flow of work visible, change the system so it improves, and automate the reporting so leaders see the truth without asking for it.

Based in
Brazil (UTC−3), working remotely
Certifications
Professional Scrum Master I · Kanban System Design (KMP I) · Management 3.0 Fundamentals · Claude Project Professional (Uniagil)
Courses
Anthropic: Agent Skills, Model Context Protocol, Building with the Claude API
Education
MBA, Leadership, Innovation and Management 3.0 (PUCRS) · BSc Information Systems (UFG)
Tools
Jira · Azure DevOps · Asana · Monday · Slack · BPMN · Claude Code and MCP

Questions

Before you write

What does it cost?

The Health Check is US$4,500, fixed. The first three clients pay US$3,000 in exchange for a named case study. The Fractional Delivery Lead starts at US$5,000 a month and Status on Autopilot at US$6,000. Invoices are in US dollars.

What happens on the 20-minute call?

You tell me about one date that worries you, and I ask about your team and tools. You leave with the first metric to check in your tracker and an honest answer on whether a Health Check fits. If it doesn't, I'll say so.

Will the time zones work?

I work 08:00–18:00 Brazil time (UTC−3, no daylight saving). That covers the full working day on the US East Coast and your afternoon in the UK and Europe.

Will this add meetings for my engineers?

No. The Health Check needs a kickoff, a few 30-minute interviews and the readout: about 4 hours of your team's time across 10 days. Later, I remove meetings that don't change a decision.

What access do you need?

Read-only access to your tracker and to the Slack channels we agree on. No code and no customer data. I'm happy to sign your NDA.

Which tools do you work with?

Jira, Azure DevOps, Asana and Monday, with Slack. If you use something else, ask on the call.

How do contracts and payment work?

A short statement of work in English, invoiced in US dollars and paid by bank transfer. For the Health Check, half at the start and the second half after the readout, only if it delivered everything listed.

What if the problem isn't process?

If it's architecture, hiring or code quality, I'll tell you on the call and point you to the right kind of help.

20 minutes, free, on video

Your next slip is already in your tracker. Let's find it.

Tell me about one date that worries you. You leave the call with the first metric to check, and an honest answer on whether a Health Check is worth it.

I work 08:00–18:00 Brazil time.

I reply within one business day. Prefer LinkedIn? Message me there.

Your message

Send it to

Open in email app

Request a 20-minute diagnostic