BUYING CUSTOM SOFTWARE

    How to get a quote for custom software

    What to prepare, what a real quote must contain, and how to compare two numbers that look nothing alike.

    7 min read

    The short answer

    To get a useful quote for custom software, bring four things: a list of the tools you pay for with monthly costs, the manual jobs your team repeats weekly, the number of people who will log in, and the one outcome that justifies the project. A real quote then itemises scope, prices changes, states ownership, sets a payment schedule and commits to a delivery window in weeks.

    What a Real Quote Has to Contain

    A number on its own is not a quote. Before you can compare two prices you need to know what each one buys. A quote you can actually act on names the scope line by line, says what happens to the price when the scope changes, states who owns the finished system, and puts a date on delivery rather than a season.

    Line to look forWhy it matters
    Itemised scopeYou can cut one item instead of renegotiating the whole build.
    Change pricingTells you the cost of the request you have not thought of yet.
    OwnershipDecides whether you are buying an asset or renting access.
    Payment scheduleShows the real cash requirement, not the headline figure.
    Delivery windowA range in weeks is a commitment; "when it is ready" is not.
    What happens after launchSupport and changes are where most budgets quietly go.

    What You Need Before You Ask

    Quoting stalls when the person asking cannot describe the work. You do not need a specification. You need four things: the tools you currently pay for and what each one costs per month, the jobs your team does by hand every week, the number of people who will log in, and the one outcome that would make the project worth doing. That is enough for anyone competent to price the work.

    Why Custom Work Cannot Be Priced From a Table

    A packaged product has one price because everyone gets the same thing. Custom work does not. Two companies in the same industry can need a five-figure difference in build because one has three staff and one has forty, or because one needs invoicing and the other needs scheduling and stock. Any agency handing you a fixed menu is either selling a template or padding the number to cover the unknowns.

    The fastest way to a real number is a list of what you pay for now.

    Fifteen subscriptions with their monthly costs tells a builder more about your business than a twenty-page brief.

    How Our Quoting Works

    We start with a discovery call of 45 to 60 minutes. It is a conversation about how your business actually runs, not a sales script. Afterwards you get a written presentation within 7 to 10 days that lays out the recommended platform, the capabilities included, the delivery window and the price. Build windows run from 2 to 8 weeks depending on scope, and the ongoing cost is a monthly subscription set at a fraction of what a comparable stack of separate tools costs.

    Questions to Ask About Any Quote You Receive

    Ask what is excluded, not what is included. Ask what the same work costs in twelve months when you need a change. Ask who holds the accounts, the code and the data if the relationship ends. Ask for the delivery window in weeks. If the answers get vague at that point, the number was never firm.

    A quote is a description of the work with a price attached. If you cannot see the work, you have not been quoted, you have been guessed at.

    From the people who build these

    Nearly every quote request that arrives with a list of current subscriptions gets priced accurately the first time. Requests that arrive with a paragraph of goals need a second call before any number is honest.

    There's a better way.

    Quoting is only fast when the builder can see the whole picture: what you run now, what your team repeats by hand and what you want reported back. Those are the same three things the platform has to cover.