Answered on : 2026-09-12 Yes, **it can be okay to do some level of requirement gathering before a proposal and contract are signed**, but it depends on the depth of the work and how it is managed. A common approach is to perform **initial discovery or high-level requirement gathering before the contract** so that you can prepare an accurate proposal, estimate costs, define scope, and understand the client's needs. Requirements gathering is often considered an early project planning activity that helps teams understand stakeholder needs and avoid scope and budget problems. [3 ] However, there is an important difference between: 1. **Pre-sales discovery (usually acceptable before signing)** - Understanding the client's goals and problems. - Asking high-level questions. - Identifying major features, constraints, users, and expectations. - Creating rough estimates or a proposal. 2. **Detailed requirements analysis (usually should be paid work)** - Writing a complete Software Requirements Specification (SRS). - Creating detailed workflows, user stories, acceptance criteria, wireframes, or technical designs. - Conducting many stakeholder interviews. - Producing documents that become project deliverables. Detailed requirement documentation requires significant professional effort. Doing too much before a signed agreement can create risks: - The client may use your document to hire another vendor. - The scope may expand without compensation. - You may spend many unpaid hours before knowing whether the project will proceed. - Expectations may be created before commercial terms are agreed. A better practice is: 1. **Before contract** - Conduct a discovery session. - Prepare a brief requirements summary. - Identify assumptions and open questions. - Include a paid discovery phase if the project is complex. 2. **After contract signing** - Perform detailed requirement gathering. - Produce formal documentation. - Obtain client approval/sign-off before development begins. A contract or agreement is important because it protects both parties by defining responsibilities, scope, and expectations. Working without a written agreement creates unnecessary risk. [4 ]

**Recommended approach:** Offer a free initial discovery call, but treat detailed requirement documentation as a paid activity. Many professional service companies use a separate **Discovery Phase / Requirements Analysis Agreement** before starting the full project. The latest shared questions What is an Ecossaise and its significance in music history? **What Is the Time Limit for Bringing a Federal Attempted Murder Charge?** What is the significance of the Starbucks at Kanazaki and what unique features does it have? **What are HSBC Central branch Saturday opening hours?** **Should I say "how much toast" or "how many toast"?** What Should I Do for a 6 Month Anniversary? ## What Are the Best Ways to Make a Logo? **What is EGM Partners and what services does it provide?** **Where can I find test papers or learning resources for “東大技高英文 第一冊” (Tung Ta Vocational High School English Book 1)?** **How to Use “Inclination” Correctly in English?** Trending shared questions **Why is Somaliland President Abdirahman Mohamed Abdullahi Irro visiting Washington to strengthen ties with the United States?** ## What is a REHAU double-glazed window gasket (seal) and how do you choose the right one? **What are the 20 best products to sell on Amazon USA as an FBA seller to potentially reach $10K/month in 2026?** **What NFL game is scheduled for September 9, 2026?** ## What is the latest information about typhoons and how can people check reliable forecasts? ## Is Google Chrome Down Right Now? # What Makes Hiromitsu Ochiai’s Autographed Items Valuable? **When Is the CPI Report This Week?** **What is Google (Alphabet) stock price and what are the key investment considerations?** What Does “Skin-Deep Issue” Mean? محمد اسماعیلی اوندری sodium chloride informed consent chicken recipes sweden language