Software development servicesThree ways we work.
One way we behave.

Whichever you pick, you get the same people, the same scope-first habit and the same fortnightly review. The detail below is the detail we would put in the SOW.

Built Data & AI Embedded

01 — Built

A product, scoped and shipped

A written scope, a fixed first increment, working software inside six weeks. Then we keep going or we hand it over.

What you get

A two-page SOW three days after the call: in, out, cost

A fixed first increment, six weeks, in your cloud account

A fortnightly review: shipped, slipped, cost against plan

A handover pack: runbook, tests, a recorded walkthrough

Good for

— A new product or module with a deadline

— A rebuild the in-house team cannot fit in

— An MVP that has to survive its first customers

Engagement · [Client]

Day 3 · The scope

Scope v1

Signed · day 3

InIngest service · DLQ + replay · runbook

OutWarehouse schema · dashboards

Terms6 weeks, fixed · NET 14

Two pages. Before you pay anything.

First engineer in

10 working days

Notice

30 days, either side

Delivery Centre

Lahore, Pakistan

Minimum term

3 months rolling

Engagement

Fixed scope, per increment

Quoted after the call · NET 14 · IP yours on payment

Ask about a scoped build →

02 — Data & AI

Systems that stay correct

Pipelines, warehouses, retrieval and evaluation harnesses. We measure the thing before we claim it improved.

What you get

Ingest and warehouse work that the in-house team can run after

Retrieval and LLM features with an evaluation harness, not a demo

Dashboards people stop arguing with

A before-and-after measurement on every increment

Good for

— Reporting nobody trusts

— A nightly batch that is now a daily problem

— An AI feature that has to be right, not impressive

Engagement · [Client]

Week 6 · Measured

First increment, live.

Measured before we claim it improved

Nightly batch

[BEFORE] → [AFTER]

Failed runs / week

[BEFORE] → [AFTER]

First engineer in

10 working days

Notice

30 days, either side

Delivery Centre

Lahore, Pakistan

Minimum term

3 months rolling

Engagement

Project or retained

Scoped on the call · NET 14

Ask about your data systems →

03 — Embedded

Engineers inside your team

Your standups, your board, your repo, your definition of done. We manage the person; you direct the work.

What you get

A named engineer, senior-led, in your standup from day one

Your tooling, your repo, your board — nothing of ours to adopt

We manage performance, holidays and cover; you manage the work

If it is not working, a replacement inside ten working days

Good for

— Scaling a team without a six-month hiring round

— A nine-month push with a hard date

— Covering a leaver while you hire properly

Engagement · [Client]

Day 10 · People in

[ENGINEER]

Backend · [YEARS]

in your standup

[ENGINEER]

Data · [YEARS]

in your standup

a41f2cingest: replace cron with queue consumerday 10 · 14:02

9be0d7dlq: replay endpoint + testsday 11 · 10:47

c07a11runbook: on-call steps, rollbackday 12 · 16:15

First engineer in

10 working days

Notice

30 days, either side

Delivery Centre

Lahore, Pakistan

Minimum term

3 months rolling

Engagement

Monthly, per engineer

3-month minimum · 30 days’ notice

Ask about adding engineers →

Eight things we do, in detail.

One page each

01Custom softwareBuilt · fixed scope per increment→02Team augmentationEmbedded · monthly, per engineer→03Data engineering & analyticsData & AI · project or retained→04AI & machine learningData & AI · project or retained→05Cloud & DevOpsEmbedded or Built→06Legacy modernisationBuilt · fixed scope per increment→07MobileBuilt · fixed scope per increment→08QA & test automationEmbedded · monthly, per engineer→

Inside every engagement.

Not extras. Not line items.

Code review

Every change reviewed by a second senior before it lands.

CI from day one

Tests and a pipeline before the first feature, not after the first incident.

Runbooks

On-call steps and rollback written as we go, in your wiki.

Documentation

Decisions recorded where your team will find them.

Security basics

Secrets, access, dependencies: handled, and listed in the handover.

Handover

A recorded walkthrough and a week of questions answered, included.

What we work in.

Only what we have shipped to production

Backend servicesFrontendData pipelinesWarehousingRetrievalEvaluation harnessesPlatform & CIObservabilityPaymentsAuth & SSOSearchMigrations

Event streamingBatch → incrementalAPI designMobileReportingModel servingCost controlOn-call runbooksData qualityIntegrationsAccess controlLoad & scale

Not on the list? We will say so on the call, rather than learn it on your time.

How an engagement runs.

See it play out →

Day 0

The call

You describe the problem. We say on the call whether we are right for it, and what it would cost.

Day 3

The scope

A two-page SOW: what is in, what is out, what it costs. Before you pay anything.

Day 10

People in

Access, first commit. You meet the engineers before they start, and they are in your standup from day one.

Week 6

First increment live

Working software in your environment, measured before we claim it improved.

Fortnightly

The review

Shipped, slipped, cost against plan. Continue, or hand over. Your call, every fortnight.

Services · the call

Tell us the problem. We will tell you which of the three it is.

Bring the problem, not a brief. If it is outside what we do well, we will say which of our contacts to call instead.

Book a consult See our work

Or email info@hopsig.com — reply within one working day.

A product, scoped and shipped

A written scope, a fixed first increment, working software inside six weeks. Then we keep going or we hand it over.

What you get

A two-page SOW three days after the call: in, out, cost

A fixed first increment, six weeks, in your cloud account

A fortnightly review: shipped, slipped, cost against plan

A handover pack: runbook, tests, a recorded walkthrough

Good for

— A new product or module with a deadline

— A rebuild the in-house team cannot fit in

— An MVP that has to survive its first customers

Systems that stay correct

Pipelines, warehouses, retrieval and evaluation harnesses. We measure the thing before we claim it improved.

What you get

Ingest and warehouse work that the in-house team can run after

Retrieval and LLM features with an evaluation harness, not a demo

Dashboards people stop arguing with

A before-and-after measurement on every increment

Good for

— Reporting nobody trusts

— A nightly batch that is now a daily problem

— An AI feature that has to be right, not impressive

Engineers inside your team

Your standups, your board, your repo, your definition of done. We manage the person; you direct the work.

What you get

A named engineer, senior-led, in your standup from day one

Your tooling, your repo, your board — nothing of ours to adopt

We manage performance, holidays and cover; you manage the work

If it is not working, a replacement inside ten working days

Good for

— Scaling a team without a six-month hiring round

— A nine-month push with a hard date

— Covering a leaver while you hire properly

Software development servicesThree ways we work.One way we behave.

A product, scoped and shipped

Systems that stay correct

Engineers inside your team

Eight things we do, in detail.

Inside every engagement.

What we work in.

How an engagement runs.

The call

The scope

People in

First increment live

The review

Tell us the problem. We will tell you which of the three it is.

A product, scoped and shipped

Systems that stay correct

Engineers inside your team

Eight things we do, in detail.

Inside every engagement.

What we work in.

How an engagement runs.

The call

The scope

People in

First increment live

The review

Software development servicesThree ways we work.
One way we behave.