All toolsWriting & Proposals
Freelance Proposal
Describe the client's problem and get back a scoped, priced proposal you can send.
Describe the client's problem and get back a scoped, priced proposal you can send.
Describe a client's software project in plain words and get back a first-draft proposal in seven fixed sections, ready to edit and send. It is built for developers and freelance software consultants: the draft always includes a tech-stack table, a phased timeline and a price range in Indian rupees.
The problem summary restates the brief in two or three sentences, so you can check you understood the client. In scope and out of scope are two bullet lists; most disputes are about what the client assumed came along, so read the second list hardest. The tech-stack table gives component, technology and reason. The timeline table gives phase, duration and deliverables and ends with a total in weeks. Risks and assumptions is a numbered list of questions to settle before you start, and the last section is a short discovery message to paste into an email or chat.
The template asks for a range in Indian rupees (₹) with one paragraph of justification, whatever currency your budget hint uses, so a hint of $2,000 can still come back as a rupee range. The model knows nothing about your rate, your market or how much you want this job: convert the currency, put in your own figure and keep the justification only if it is true for you.
You need to be signed in, because every proposal is a call to Google's Gemini API (Gemini 2.5 Flash-Lite). The description can be up to 8,000 characters; longer text is rejected, not cut. Each hint is cut to 500 characters. One IP address can generate 15 proposals per 10 minutes. The proposal is not saved anywhere, so copy it before you start a new one.
The draft never mentions tax, so add a line saying whether your price includes GST. Under section 22 of the CGST Act, 2017, a supplier of services must register once aggregate turnover in a financial year exceeds ₹20 lakh (₹10 lakh in some special category states); once registered, you add GST to the fee for clients in India. Work for a client outside India usually counts as an export of services if it meets the conditions in section 2(6) of the IGST Act, 2017, including payment in convertible foreign exchange or in rupees where the RBI permits. Exports are zero-rated under section 16 of that Act: with a Letter of Undertaking (LUT) filed on the GST portal, you invoice them without charging IGST. Discuvr does not work out tax for you; check your own case with a tax adviser.
Edit it first. The structure is reusable, but the price is a rupee placeholder and the dates, terms and stack have to be yours.
What the client asked for, who will use it, the platforms, any integrations (payments, login, an existing database), constraints they mentioned and the rough budget or deadline if you know it. Vague input gives a vague proposal.
It is tuned for software work: it writes as a software consultant and always adds a tech-stack table. For design, writing or marketing work, keep the scope, timeline and out-of-scope sections and delete the stack table.
Not by Discuvr. The description and hints are sent to Google's Gemini API to write the draft; the usage record keeps only the description's length and which of the three hints you filled in. Leave out names and details you may not share with a third-party service.
No. The seven sections stop at scope, stack, timeline, price, risks and a first message, so add three terms yourself before sending: the payment schedule (for example an advance, then a payment as each timeline phase is delivered), how many rounds of changes the price includes, and when the code becomes the client's. Under section 17 of India's Copyright Act, 1957, the author is the first owner of a work, and the employer exception covers employees, not freelancers; under section 19, an assignment of copyright is valid only in writing signed by the assignor. A client who expects to own the code therefore needs a signed assignment clause.
Copy markdown copies the raw text, so a plain paste into Word or Google Docs shows each table as rows of | characters and each heading with # marks. For Word, select the formatted proposal on the page with your mouse, copy it and paste: headings, lists and tables arrive as real formatting. For Google Docs, turn on Markdown once (Tools, then Preferences, then Enable Markdown), press Copy markdown and paste with right-click, Paste from Markdown, which Google added in July 2024; a normal Ctrl+V still pastes the raw text. Use Copy markdown as it is wherever markdown is read directly, such as a GitHub issue or README.
The draft always quotes a fixed range tied to the phases in its Timeline table, which suits work whose In Scope list you can describe completely. Check the range against your own rate before sending: count the working days across the timeline phases, multiply by your day rate and add a margin for the open items in Risks & Assumptions. If the brief is still vague, or the work is ongoing support, quote a day or hourly rate with an estimate of the hours instead, and keep the In Scope and Out of Scope lists so the client sees what the estimate covers.
Get the client to agree to the two lists the draft already has before you start: Out of Scope names what the price excludes, and Risks & Assumptions names what the client still has to confirm. When a new request arrives later, check it against Out of Scope, reply with a short change request (what changes, the extra days and the extra price) and begin only after the client approves it in writing, even by email. For a large addition, describe only the new work here and generate a separate proposal for it, so the original price and timeline stay as agreed.