Software · Cloud · Business process

Price the outcome.
Or hold the team.

Goodwin Engineering Co builds and runs software, cloud and back-office operations for mid-market companies. Take a fixed-bid scope when the work is known, or a dedicated team when it isn't. Same engineers either way.

Request a scope Compare the models
  • Fixed price means fixed price
  • Named team, no shared seats
  • Paid pilot before you commit

Try a model

Indicative pricing

You buy a defined outcome

We price the whole scope and absorb the estimate risk. If it takes more hours than we planned, that's ours to carry.

Locked

  • Price
  • Scope
  • Delivery date

Flexes

  • Our staffing
  • Sequencing
  • Method

Typical engagement

$25k – $400k 6–30 weeks · billed on milestones
Get a fixed-bid estimate

Delivered under

  • ISO 27001 certified
  • SOC 2 Type II ready
  • GDPR & DPDP aligned
  • 24×5 coverage, 24×7 P1

What we run

Six service lines, one delivery standard.

Every line is available as a fixed-bid project. The lines that never really finish are available as a dedicated team.

Application development

Feature delivery, refactors, version upgrades and L2/L3 support across web, mobile and internal systems.

Fixed bidDedicated team

Cloud & infrastructure

Migration, infrastructure as code, cost tuning and round-the-clock monitoring on AWS, Azure and GCP.

Fixed bidDedicated team

QA & test engineering

Regression suites, automation frameworks, performance testing and release gates wired into your pipeline.

Fixed bidDedicated team

Data operations

Migration and cleansing, annotation and labelling, reporting pipelines, and recurring data entry at volume.

Dedicated team

Customer support operations

Tier 1 and 2 desks over email, chat and voice — run to your SLA, in your tooling, with your macros.

Dedicated team

Finance & accounting

Accounts payable and receivable, reconciliation, invoice processing and month-end close support.

Dedicated team

Engagement models

The difference isn't the team. It's who carries the estimate risk.

Same engineers, same standards, two contracts. Pick the one that matches how certain the scope is on the day you sign.

Model A

Fixed bid

A defined outcome at an agreed price.

Model B

Dedicated team

A named team for a set period.

01Estimate risk
OursOverruns come out of our margin, not your budget.
YoursYou decide what the team spends its sprints on.
02Handling a change
Change orderPriced and approved before work starts.
ReprioritiseAt any sprint boundary. No re-pricing.
03Billing
Milestones30% kickoff · 40% UAT · 30% sign-off.
MonthlyPer team, invoiced in arrears.
04You need
Requirements you can signA scope that will hold still for the duration.
A product ownerSomeone on your side to set priorities weekly.
05Commitment
Per project6–30 weeks, ends at delivery.
3 months, then rollingResize or exit on 30 days' notice.
06Best for
Known workMigrations, integrations, compliance, defined builds.
Work that keeps goingProduct roadmaps, ongoing ops, maintenance.

Not sure which fits? Most clients start fixed bid on a first project, then move to a dedicated team once there's a roadmap worth staffing.

Ask us which one fits

How an engagement starts

From first call to steady state in about six weeks.

0145 minutes

Discovery call

What the work is, what's already built, and which model fits. No deck, no discovery fee.

025 business days

Scoped estimate

Fixed bid gets a line-item price and milestone plan. A team engagement gets a team shape and rate card.

032–4 weeks

Paid pilot

A real slice of the work — first milestone or first two sprints — before either side commits further.

04Ongoing

Steady state

Weekly demo, monthly delivery report, and one named delivery lead who answers for the work.

Coverage

Three centres, deliberate overlap.

Teams are placed so there's live overlap with your working day, and a handover — not a silence — when a shift ends.

  • 4h+Daily overlap with US and EU hours
  • <15mP1 acknowledgement, any hour

Delivery coverage · 24h UTC

Loading…
Bengaluru · IST
Kraków · CET
Austin · CT
00040812162024

Before you ask

The questions procurement always asks.

If yours isn't here, put it in the brief and we'll answer it in writing before the call.

What happens if a fixed-bid project overruns?
We absorb it. The price on the contract is the price on the invoice. The only thing that changes it is a change you ask for, and that gets priced and approved before anyone starts work on it.
Who owns the code and the IP?
You do. IP assigns to you on payment under the master services agreement, including anything written during a paid pilot. We keep no licence over your work product.
Can we start small before committing?
Yes — every engagement starts with a paid pilot of two to four weeks. It's real work against your backlog, not a proof of concept you throw away, and either side can stop at the end of it.
Is the team dedicated, or shared across clients?
Dedicated. You get names, calendars and standup access, and nobody on your team is allocated to another account without your written sign-off.
How do we exit a dedicated team engagement?
Thirty days' written notice, any time after the initial three months. The last two weeks are handover: documentation, runbooks and a walkthrough with whoever picks the work up.
Will the team work our hours?
There's at least four hours of live overlap with your working day, every day. Standups, demos and incident response happen inside that window.

Request a scope

Tell us what needs building or running.

Send the outline and we'll come back within two business days with the model we'd recommend and what it would cost. If we're not the right fit, we'll say so on the call.

Send a brief

Four fields. A real person reads every one.

Tell us who you are.

We need the company name.

Use an address we can reply to.

Model you're considering

A sentence or two is enough to start.

We reply to every brief, including the ones we turn down.

Rather just talk it through?

Forty-five minutes, no deck, no discovery fee.

Book a discovery call