Writing a software development Proposal.

  • VAI

    SSC Enthusiast

    Points: 115

    I need to write a Proposal to a client to develop a small software for them (up to 10K priced).

    However, I cannot find an example or template for such purposes.

    Can someone please help?

    thank you

  • VAI

    SSC Enthusiast

    Points: 115

    All Google searches for 'How to write a software development proposal'

    or 'Application Development proposal example' return only 100s of commercial offers , marketing 'Buy template' ,etc.

    It is a small application (2 excel spreadsheets: 1st contains input data , 2nd builds a Geographical visualization of it (on map). PoweBI can be used, too. Later a database will be involved, and same functionality developed as 2 web-pages later on.

    How long should my Proposal be? Does a strict order of sections matter?

     

  • Jeff Moden

    SSC Guru

    Points: 997150

    Write a section that identifies the purpose/problem this will solve. (Problem Overview)

    Write a section on how the spreadsheets, etc, will solve the problems.  If you have additional advantages, such as how easy your methods will also support PowerBI and 2 web pages, then include those, as well. (Recommended Solution)

    Write a more detail functional section that explains the working parts in more detail. (Functional Description)

    Write a section that explains the costs and ROI. (Costs and ROI).

    Then, go back to the beginning and write and 3 or 4 sentence "Executive Summary" section that summarizes it all.

    If there are any terms that need explaining (and remember your target audience), include a short glossary.

    Add a table of contents right after the "Executive Summary" (easiest done if you use Word Headers in the rest of your document, which should usually be limited to 3 levels at least in the TOC).

    And a cover page followed by a "Revision History" page or include the revision history at the bottom of the cover page.

    Get someone to review the document well prior to you submitting it to the people that you ultimately want to see it and make a decision.

     

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    "Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

  • Mr. Brian Gale

    SSC-Insane

    Points: 23167

    Another thing to add in to what Jeff said is if you are a contractor working on this, make sure to include your support costs for if/when the application fails.  For example, if the end user upgrades Excel, will your application continue to work?  What if they have an ancient version that they use (such as 2000), does your application support that?

    As this is your first software development proposal, I would start by writing one following Jeff's advice and then save that somewhere.  Next, modify it to be as generic as possible so you can use it for a template in the future.

    Last thing to remember with the cost of software is the cost of software support.  How long are you offering support for with the cost of the software?  Is support a paid service or is it included for the lifetime of the product?  I wouldn't include that in the software development proposal, but make sure to get it in writing so everyone is on the same page in terms of support.  May want to figure out payment terms too.  Is it payment on successful delivery of the tool or 10% up front or payment at each milestone?

    Also, get as much communication related to the project in writing and get sign off on all documents from the stakeholders.

    Most of my advice above is unrelated ot a software development proposal, but it is stuff you will want to keep in mind while developing it.  Also, make sure to get things "feature locked" prior to development starting.

  • Jeff Moden

    SSC Guru

    Points: 997150

    Brian hit a nail on the head that I totally forgot about and that's to be sure you include what he said about support, what's supported or not, and that changes in-scope will require new pricing and that there is no guarantee.  You might want to check on other EULAs like the one Microsoft has for every one of their products that basically protects them for any and all ramifications of use, disuse, abuse, suitability, etc, etc, ad infinitum.  If you're going to consult, get a lawyer that's skilled in such things to help you.  Find a good set of EULAs, etc, and have the lawyer look them over.

    --Jeff Moden


    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
    "Change is inevitable... change for the better is not".
    "Dear Lord... I'm a DBA so please give me patience because, if you give me strength, I'm going to need bail money too!"

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply