The tool your team actually uses.
Intake and CRM tools, customer portals, quoting systems, marketplaces, dashboards, and the integrations between them (Stripe, QuickBooks, GoHighLevel). Designed first, then built. From $15,000.
| Delivers | Discovery and workflow map · UX design and a clickable prototype approved before code · build on Next.js, Postgres, Vercel · tests · deploy · documentation and recorded training · 30 days of support |
|---|---|
| Timeline | 4–12 weeks |
| Billing | Deposit + milestones, fixed scope |
| From | $15,000 |
| You own | Code (your GitHub), hosting (your Vercel), data (your database) |
Vector UX designs and builds custom software for small companies: internal portals, quoting tools with customer e-sign, marketplaces, dashboards, and integrations with the systems you already use. Every build starts with a workflow map and a clickable prototype you approve before code. Builds start at $15,000, take 4–12 weeks, and are billed by milestone.
Where projects land
| Scenario | Example | Range | Timeline |
|---|---|---|---|
| Internal portal or dashboard | One place for jobs, customers, and status, replacing three spreadsheets and a group text. | $15,000–$25,000 | 4–6 weeks |
| Quoting tool with customer e-sign | Upload a plan, build a quote from your price book, send a link the customer selects options in and signs. | $18,000–$35,000 | 6–8 weeks |
| Marketplace or multi-vendor platform MVP | Vendors list, buyers order from several at once, payouts split automatically. | $40,000–$80,000 | 12–16 weeks |
What moves the number: payments (+$1,500) · customer or team login (+$4,000) · integration with a system you already use (+$2,500) · e-signature and locked approvals (+$2,500) · reporting and exports (+$2,000) · an ai feature (+$6,000). Try the estimator →
When we tell you to buy instead
About a third of the companies that talk to us should buy an off-the-shelf product, and we say so on the first call. Custom software wins when the workflow is yours, when the off-the-shelf tool makes your team work its way, or when the data has to connect to something the vendor does not support. It loses when a $50-a-month tool already does 90% of the job.
- Buy when a known tool does 90% and your process is standard.
- Build when the workflow is the business, or when nothing connects to your data.
- Build small first: one workflow, one team, one month.
How the build runs
Discovery maps the workflow and produces a prototype. You approve every screen. Then weekly demos and a staging link until launch, with tests on anything that moves money or data. Documentation and a recorded training session are part of the scope, not an extra.
How it runs
Asked before
How do you price a custom build?
What if we should buy software instead of building it?
Who owns the code?
What happens after launch?
Can you work with our existing developer?
Tell us what you're building.
30 minutes, no deck. You'll leave with a scenario and a price range.