Skip to main content

What are you looking for?

Explore our services and discover how we can help you achieve your goals

Client Workspace

Software Development Company Red Flags in Proposals, Contracts and Demos

The red flags that predict a troubled software project are visible before signing, in the proposal, the draft contract and the sales demo. Netbase JSC suggests reading all three together, rating each sign by severity and asking for the evidence that clears it, so a warning becomes a question with a written answer.

Book a solution review Compare engagement models

By Netbase Delivery and Quality Desk · Reviewed by David (CEO) · Updated · 10 min read

star

This guide is for founders, CEOs, procurement and IT leads who are comparing two or three companies for a custom build, a platform change or an AI project. It belongs to the partner-selection series that starts with choosing a large or boutique Vietnam IT vendor, and it covers the checks to run before custom software development work is signed.

In this guide

Why do most red flags appear before the contract is signed?

A troubled project rarely starts with bad code. It starts with a gap between what the buyer needs and what the company promised, written down before the first sprint. The proposal shows how well the company understood the problem, the contract shows who carries the risk when the understanding was wrong, and the demo shows whether the team can build what it describes.

Published red-flag lists agree on the common signs. A 2026 guide from Madgeek names an estimate that arrives within 48 hours without discovery, no technical person in the sales process, a company that agrees to everything, a team assembled only after signing and a contract with no code access. A Directio guide adds the bait-and-switch: senior people at the pre-sale meetings, then a junior team with little oversight once the contract is signed.

Those lists do not say where a buyer sees each sign, how serious it is, or what answer would make it harmless. The matrix below adds all three.

Which red flags matter most, and what clears them?

Severity in this matrix means: stop (do not sign until it is fixed in writing), test (ask for evidence and decide on the answer) and note (worth one question, rarely a reason to walk away).

Where you see it Red flag Severity What clears it
Proposal A fixed estimate with no discovery, or an estimate the company cannot explain Test A written list of assumptions and a discovery step before the estimate is binding
Proposal A feature list with no business outcome and no out-of-scope list Stop The outcome, the out-of-scope items and the acceptance criteria per milestone in the same document
Proposal No named roles, or the team is only "assembled after signing" Test Named roles (project manager, architect, QA), how the team is formed and who you meet before kickoff
Contract A licence to the code instead of ownership of custom work, or no repository access Stop IP assignment for custom code, repository access during the project, and licensed components listed separately
Contract Payments tied to calendar dates rather than accepted milestones Test Each payment linked to a milestone with written acceptance criteria
Contract No change-control clause, or changes priced only "as needed" Test A change request process that shows scope and schedule impact before work starts
Demo Slides or a design prototype only, no working software Test A running build of a similar system, or a short paid pilot with a working result
Demo The people who demo will not work on your project Note A meeting with the delivery lead and the escalation path written into the contract
AI use "AI-powered delivery" with no human review step or no data-use statement Stop Where AI is used, who reviews its output, and what happens to your code and data

One stop item is enough to pause a signature. Three or more test items from the same company usually mean the proposal was written before the company understood the problem. The demo rows follow a principle of the Agile Manifesto: working software is the primary measure of progress, so asking to see something run is fair.

How to turn a red flag into a written answer before signing

  1. Read the three documents side by side

    Put the proposal, the draft contract and your notes from the demo next to each other. Many signs only appear when they disagree.

  2. Mark each sign with its severity

    Do not reject a company for a note item; do not sign over a stop item.

  3. Send every stop and test item as a question

    Ask for the answer in writing, not on a call.

  4. Ask for the evidence, not the promise

    A clause, a sample acceptance document, a running build or a named role clears a sign. "We always do that" does not.

  5. Check that the answer reaches the contract

    A good answer in an email that never reaches the signed terms is still a red flag.

  6. Compare how each company handled the questions

    A company that answers quickly, admits what it does not do and changes the documents is showing how it will behave during delivery. After signing, keep the same record in a reliability ledger.

For scope clauses in particular, the guide to spotting scope-creep risk in a proposal reads the wording line by line. A scoping guide from Charter Global makes the same point from the delivery side: a feature list without a defined outcome invites scope creep, because no one can show that a new request is out of bounds.

Where AI fits

AI changes both what a buyer should check and how the check can be done. On the buyer's side, AI can compare three proposals against the brief, list missing acceptance criteria and highlight clauses that differ from the draft contract; a person still decides what is a red flag and what is a reasonable trade-off. On the company's side, AI-assisted delivery is a red flag only when nobody reviews the output or the company cannot say what happens to your data. Netbase works with the major commercial and open-source AI tools and models, chosen per project.

The delivered AI feature named with a client is 4over4's recommendation engine, which suggests products from browsing history and previous purchases. Beyond it, Netbase has delivered AI projects for clients that are not named, including retrieval-augmented knowledge assistants, document AI and MLOps pipelines. To see how an AI-using company should describe its review, compare AI-augmented and AI-native companies in a proposal.

When is a warning sign not a red flag?

Some signs are normal in the right context. A quick estimate is reasonable for a small, well-defined package with a standard scope. A demo of a reference build, rather than of your future system, is normal before discovery; what matters is that the company says so. A standard licence is correct for productized modules the company owns and maintains, as long as the custom work written for you is yours.

Treat a sign as a red flag when it is hidden, not when it is explained. The test is whether the company states the condition openly and puts it in the documents.

What delivery record exists, and what does not

The first contact at Netbase JSC is the CEO, Huy Nguyen (David), by WhatsApp or email, and every service is delivered remotely to clients in any country and industry. Consulting, solutions, custom development and AI-enabled transformation are Netbase's lead offers, with dedicated teams and outsourcing as secondary options.

Delivery follows a six-step lifecycle: discovery and strategic alignment, team assembly and architecture planning, agile execution with outcome-based milestones, modular and productized components, training and rollout, then ongoing support. Most Netbase projects are delivered on fixed-price contracts; milestone-based, monthly team retainer and KPI-linked models are also offered. Governance runs through weekly reviews, KPI dashboards and a dedicated account manager and project manager.

For custom development, the client owns the IP created for it; Netbase productized modules and Business Division products are licensed, not transferred. Netbase holds ISO 27001 certification and a SOC 2 Type II attestation for its own operations. Netbase also works as offshore development partner on a multi-tenant cloud ERP for a US client that is not named.

What does not exist: Netbase publishes no count of troubled projects it has taken over, no failure rate and no figure on how often these red flags appear in the market. This guide claims none of them.

Alternatives: which other checks should you run before signing?

Choose the vetting method by the risk you need to remove.

Method Best for Limit Choose it when
Red-flag review of proposal, contract and demo Finding mismatches before signature Depends on what the company writes down You have two or three proposals and a draft contract
Reference calls with past clients Checking behaviour under pressure The company chooses the references The project is long or the switching cost is high
Paid pilot or discovery phase Seeing working software and the real team Takes time before the main contract The scope is still open or the technology is new to you
Security and compliance questionnaire Data handling and access control Says little about delivery quality You handle personal, payment or health data
First call with a decision-maker Testing judgement and trade-offs early One conversation, not evidence You want to know who will answer for the result

The guide to a CEO-led first call covers the last method in detail, and the protecting IP when outsourcing guide goes deeper on contract terms; verifying a company's claims covers certificates and references. The Netbase engagement models page shows how project and team options differ.

Limits of this guide

  • It covers signs visible in the proposal, contract and demo; it is not legal advice and does not replace a lawyer's review of the contract.
  • Other companies are cited neutrally from their own published guides, accessed 2026-11-21, and are not ranked here.

Plan the next step with a Netbase consultant

Frequently asked questions

The most serious are a proposal with no out-of-scope list or acceptance criteria, a contract that licenses custom code instead of assigning it, payments tied to dates rather than accepted milestones, and AI use with no stated human review.

No. A fast estimate is reasonable for a small package with a standard scope. It becomes a red flag when a custom project gets a fixed estimate without discovery and the company cannot list the assumptions behind it.

Not automatically. Ask for a running build of a similar system or a short paid pilot. If the company can show neither, treat it as a sign that the team has not built what it is describing.

Check four things in plain language: who owns the custom code, when you get repository access, what each payment is tied to, and how changes are approved.

Next step

Send your shortlist's proposals or your own brief, and the reply will come from someone who can decide on it: book a solution review.

AI-enabled custom software development built around your workflow AI-enabled custom software development built around your workflow

Netbase provides custom software development for companies whose workflow no off-the-shelf product fits, from discovery through architecture, build, testing and handover, with AI where it removes manual steps and the IP left with you. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to the published USticker case study, design-tool users converted 40% more often.

Learn More
line
An AI-enabled offshore development center in Hanoi, when a long roadmap needs one An AI-enabled offshore development center in Hanoi, when a long roadmap needs one

An offshore development center (ODC) in Vietnam is a long-running engineering team that a partner abroad staffs, manages and documents for your product roadmap. Netbase runs ODC teams from its only office, in Hanoi, with AI-assisted engineering, weekly governance and knowledge transfer built in. When the work has a defined outcome, a fixed-price project usually fits better.

Learn More
line
Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system Custom cloud ERP with AI forecasting and document capture: projects, finance, HR and CRM in one system

A custom cloud ERP from Netbase is one browser-based system where a growing company runs its projects, finance, HR and customer relationships on shared data, with AI that reads invoices and forecasts demand and cash. It suits SMEs that have outgrown spreadsheets but not their own way of working, on the foundation of Cloodo Workspace, which Netbase built and runs.

Learn More
line

Work with Netbase remotely

Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.

Contact Netbase

Discuss a project

Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.
Project enquiries

project@netbasejsc.com

WhatsApp

+84 937 869 689

Office address

91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam

Get in touch

Tell us what you want to build, modernize, or operate.

Tell us what you want to build, modernize, or operate.

Contact Netbase