CUSTOM SOFTWARE PLANNING
The Pre-Build Checklist: 6 Requirements Before Coding
Bottom Line Up Front (BLUF)
80% of failed custom software projects fail before a single line of code is written. The failures originate in vague requirements, undefined success metrics, and missing compliance specifications. This 6-point pre-build checklist ensures your project has a concrete foundation before development begins, preventing the two most common failure modes: scope creep (which adds 40-60% to budgets) and post-launch adoption failure (which kills 30% of custom software projects within 12 months).
You have decided your business needs custom software. Maybe a client intake portal, a document automation system, a field operations app, or an internal reporting dashboard. Before you engage a development firm, run through this checklist. If you cannot answer all six items with specificity, you are not ready to build. That is fine. It is far cheaper to discover gaps now than during a $50K-$100K development engagement where scope changes cost $150-$300 per hour.
The 6-Point Pre-Build Checklist
Define the Single Most Painful Workflow
Do not list 15 features. Identify the ONE workflow that costs your business the most in labor, errors, or client complaints. Be specific. The statement intake is slow is not actionable. The statement new client intake requires 45 minutes of staff time across 3 separate systems with manual data re-entry between each is actionable. The specificity determines whether your developer builds the right thing or builds their interpretation of your vague description.
Quantify the Current Cost
How much does this broken workflow cost per month in loaded labor? The loaded hourly rate includes salary, benefits, payroll taxes, and overhead (typically 1.3-1.5x the raw hourly wage). Example: a paralegal at $35 per hour spends 45 minutes per intake across 40 new clients per month. Monthly cost: 40 times 0.75 hours times $35 equals $1,050 per month, or $12,600 per year. This number becomes your ROI baseline. If the software costs $15,000 to build, payback is 14 months. If it costs $30,000, payback is 28 months. You cannot evaluate whether custom software is worth building without this number.
Map Every Integration Point
List every system the new software must connect to: your CRM, accounting software, email, calendar, document storage, practice management system, ERP, or field management platform. For each system, determine three things: does a documented API exist, does your current pricing plan include API access, and what authentication method does the API use (OAuth, API key, Basic Auth). If a critical system has no API, the integration will require web scraping or manual export, which adds $3,000-$8,000 and 2-4 weeks to the project.
Specify Compliance Requirements
If the software handles client data, patient records, financial information, or employee data, specify the compliance requirements in writing. For medical practices: HIPAA (encryption standard AES-256, audit logging, BAA required). For legal firms: bar association ethics rules on data handling. For financial services: SOX audit trail requirements. For all businesses: data residency (US-only hosting), access control model (role-based), and backup/retention policy. Your vendor must confirm each requirement in writing before development begins.
Set a Binary Success Metric
Define what done looks like in one sentence. Intake time reduced from 45 minutes to under 10 minutes with zero manual data re-entry. Invoice processing time reduced from 12 minutes to 30 seconds per invoice. Daily report compilation automated, eliminating 2 hours of admin labor per day. If you cannot write this sentence with a specific before number and a specific after number, your requirements are not clear enough to build against. The success metric also protects you legally: if the vendor delivers software that does not meet the metric, you have a contractual basis for remediation.
Establish the Budget Ceiling
Determine the maximum you will spend before seeing a working prototype. A reasonable range for a focused MVP: $15K-$40K for most Houston mid-market businesses. If a vendor cannot deliver a working prototype within this range, their architecture is over-engineered for your actual needs or they are padding scope to increase the engagement size. The prototype should demonstrate the core workflow from end to end, not just wireframes or mockups.
Vendor Evaluation Red Flags
| Red Flag | What It Means | What to Do |
|---|---|---|
| Vendor starts building before you complete this checklist | They are prioritizing their billable hours over your outcome | Stop the engagement. Requirements first, code second. |
| Vendor quotes hourly with no budget cap | You are absorbing 100% of the scope creep risk | Demand a fixed-price proposal with defined deliverables |
| Vendor cannot explain their architecture in plain language | They are using complexity to justify higher fees | Ask: why does this need microservices? Often it does not. |
| Vendor has no portfolio of similar-scale projects | You are their learning experience | Ask for references from businesses your size in your industry |
For a weighted evaluation framework for comparing development firms, see our Vendor Evaluation Scorecard. For understanding the full pricing landscape for custom software in Houston, see our 2026 Pricing Guide.
Know exactly what you need before you pay to build it.
Book a Requirements Workshop
We offer a 1-week requirements engineering engagement that walks you through this checklist and produces a production-ready specification document. You own the document. Use it with any development firm.
Book the Workshop