How to choose a software contractor

A software-contractor guide is for when a portfolio and a low price are not enough. Ask what version one is, who owns the data, and what happens if the key person leaves. KGSM will ask you the same in discovery.

This guide — How to choose a software contractor — is written from KGSM delivery work: scoped first versions, staged releases, and support after handoff.

Audience, risk, and how KGSM works

An enterprise buyer choosing among software contractors with a defensible contract

A contractor without written scope, mid-project demos, and data export means lock-in and a floating date.

KGSM expects to be scored on the same tests: version one, ownership, SLA, and a real scenario.

Scope and mid-project demos

The contractor should write version one on one page. Mid-project demos use near-real data, not fake screens. If you only see the end, the risk is yours. A short weekly note beats a fifty-page monthly file.

Demand version one on one page. A cheap contractor without a repo cut access after a dispute.

Ownership, repo, backup person

Repo access or code delivery in the contract. Runbooks. A named technical owner and a deputy. A lone freelancer is risky for a finance system even if cheap. Price post-handoff support separately so a cheap build cannot hostage you.

Without a written version one the date slipped every month. Mid-project demos on your data.

How to compare bids

A table: version one, integrations, training, SLA, export, default maintenance. The cheapest row without export is the most expensive. Score KGSM on the same table.

Put export and repo in the contract. The key person left and there was no runbook.

Verbal free support died after month one. Ask for a deputy to the key person.

Price maintenance separately. A cheap contractor without a repo cut access after a dispute.

Without a written version one the date slipped every month. Write the SLA down.

Implementation checklist

• Demand version one on one page.
• Mid-project demos on your data.
• Put export and repo in the contract.
• Ask for a deputy to the key person.
• Price maintenance separately.
• Write the SLA down.

Field scenario 1

A cheap contractor without a repo cut access after a dispute.

Demand version one on one page.

Field scenario 2

Without a written version one the date slipped every month.

Mid-project demos on your data.

Field scenario 3

The key person left and there was no runbook.

Put export and repo in the contract.

Field scenario 4

Verbal free support died after month one.

Ask for a deputy to the key person.

Related KGSM pages

Continue with KGSM services: طراحی اپلیکیشن موبایل, اتوماسیون فرآیندهای سازمانی, سئو و بهینه‌سازی. Related reading: اشتباهات رایج شرکت‌ها در انتخاب نرم‌افزار سازمانی. For a scoped estimate, use the contact form.

When you apply this on a live team, write it as an operating rule, not a slide: Demand version one on one page. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Mid-project demos on your data. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Put export and repo in the contract. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Ask for a deputy to the key person. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Price maintenance separately. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Write the SLA down. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A cheap contractor without a repo cut access after a dispute. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Without a written version one the date slipped every month. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: The key person left and there was no runbook. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Verbal free support died after month one. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A contractor without written scope, mid-project demos, and data export means lock-in and a floating date. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: KGSM expects to be scored on the same tests: version one, ownership, SLA, and a real scenario. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: An enterprise buyer choosing among software contractors with a defensible contract Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Demand version one on one page. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Mid-project demos on your data. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Put export and repo in the contract. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Ask for a deputy to the key person. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Price maintenance separately. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Write the SLA down. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A cheap contractor without a repo cut access after a dispute. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Without a written version one the date slipped every month. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: The key person left and there was no runbook. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: Verbal free support died after month one. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: A contractor without written scope, mid-project demos, and data export means lock-in and a floating date. Then assign an owner and a review date so the rule survives the first busy week.

When you apply this on a live team, write it as an operating rule, not a slide: KGSM expects to be scored on the same tests: version one, ownership, SLA, and a real scenario. Then assign an owner and a review date so the rule survives the first busy week.