The cost of custom software, explained.

Effort is what you pay for, and effort comes from what the system has to do and how many other things it has to work with. A small internal tool with one team and one data source is a different job from a customer portal that connects to accounting software, sends notifications and holds records for several outside companies.

The sections below name the factors that move a quote up or down, explain why two quotes for the same idea rarely match, and give you a checklist for comparing them. For the wider picture of what a project involves, see custom software development.

Roles and permissions come first. A CRM where every user sees every record is simpler than one where sales, service and partner users each see their own. Pipelines and modules come next: one sales pipeline is less work than several, each with its own stages, fields and approvals. Quotes, tasks, reminders and dashboards each add screens and rules.

Integrations with email, calendars, accounting software and website forms add effort for each connection. Migration from spreadsheets or a current CRM depends on how clean and consistent that data is. AI agents, such as one that qualifies leads or drafts follow-ups, add a build and a review step. Support after launch is the last line to plan.

Foxefy builds CRMs and customer portals under sales and customer operations. If you are weighing a product against a build, read custom CRM vs off-the-shelf CRM.

• Scope assumptions: one firm reads "user management" as a login screen, another as roles, invitations and an audit trail.
• Team seniority: more experienced people cost more per hour and often need fewer hours and less rework.
• Team setup: where and how the team works changes what its time costs and how much management it needs.
• Pricing model: a fixed price carries a margin for risk, while time and materials passes the risk to you.
• What is included: testing, documentation, deployment, training and support after launch may or may not be in the number.
• Unknowns: a firm that has not asked about your data or integrations has priced a guess.

Buyers want clear pricing and clear contract terms, and the way to get them is to give every firm the same written brief. The software project brief template is a good starting point, because it makes quotes comparable.

A team that charges less per hour but needs long clarification cycles, redoes work after misunderstandings or cannot join your review calls can cost more in the end. A team that costs more per hour but works from a clear scope, reviews often and delivers what was agreed can cost less. Ask each firm how it handles requirements, reviews and changes, and weigh the answers beside the quote.

The same logic applies when you compare a vendor with hiring your own team. The in-house vs outsourced guide covers the costs of building a team yourself, including the ones that never appear in a salary line.

The full comparison, including how each model handles change requests, is in fixed price vs time and materials.

Foxefy starts every engagement with a discovery call over video. The call covers how your team works, the problems you want to solve and your current and future objectives, so the recommendation fits your business. The scope that comes out of it is what Foxefy quotes. Read how the call runs on the how we work page.

Skipping discovery does not remove the questions. It moves them into the build, where each answer costs more because something may already be built the other way. The timeline guide shows where discovery sits among the phases of a project.

• Task scope: an agent that drafts follow-ups is less work than one that routes requests across teams and updates several records.
• Systems touched: each system the agent reads from or writes to needs a connection, permissions and testing.
• Volume: more requests mean more model usage, which is a running cost after launch and not part of the build.
• Model usage: how often the agent calls a model, and with how much context, sets that running cost.
• Human review: an approval step adds some build effort and removes the risk of unchecked actions.

The way to judge the value against these costs is set out in measuring the value of AI agents. Foxefy builds AI agents as part of AI and automation, and its agents work within clear permissions and hand judgment calls to people.

• Hosting: servers or cloud services that run the system and store its data, plus backups.
• Maintenance and support: fixing defects, updating libraries, answering questions and making small changes.
• Third-party licenses: paid components, maps, messaging or other services the system relies on.
• API or model usage: charges from outside services that grow with how much the system is used.

ISO/IEC/IEEE 14764 (2022 edition) defines five types of software maintenance: corrective (fixing problems found after delivery), preventive (fixing latent faults before they show up in the live system), adaptive (keeping the software usable as its environment changes), perfective (improving its performance, maintainability or other qualities) and additive (adding functions or features after delivery). Asking a vendor which of these a support plan covers tells you what the support line buys. Foxefy offers support and maintenance contracts for the systems it builds.

The quote follows the scope agreed in discovery: which modules, which roles, which integrations, what happens to existing data and what support follows launch. Foxefy then builds in agile iterations with regular check-ins, so you see progress and your feedback shapes what comes next.

Foxefy works remotely, with discovery, reviews and check-ins over video calls. To start, book a discovery call.

1. Write one brief and give it to every firm. The project brief template covers what to include.
2. Check that each quote lists modules, roles and integrations, not just a total.
3. Check what happens to your existing data: who cleans it, who loads it and who checks it.
4. Check whether testing, documentation and deployment are in the quote.
5. Ask what support after launch includes and what is billed separately.
6. Ask which assumptions the quote rests on and what happens if one turns out wrong.
7. Ask how change requests are handled and priced.
8. Ask who you will talk to during the build and how often you will review progress.
9. List what each quote leaves out before you compare the totals.