Belitsoft > Discovery Phase in Software Development: How Do We Do It?

Discovery Phase in Software Development: How Do We Do It?

As a Business Development Director with nearly two decades of experience, I collaborate with clients to narrow the gap in cost estimation, even for the most complex projects, using the discovery phase. Let me share how I achieve this for our clients looking to modernize their core business app.

Contents

CLIENT

Who are our typical clients?

Our typical clients predominantly hail from the US, UK, Israel, and Canada. They're companies with a workforce ranging from a handful to several hundred employees.

They possess proprietary core business application, custom-developed to automate their key business operations.

This software often has a history spanning 10-20 years. While it remains functional, the challenges it presents are growing. Typically, it starts to run slowly, experiences downtimes, reveals an absence of mobile and remote access, and is incompatible with newer features.

Compounding these problems, the original developers who built the software are often no longer accessible. Consequently, successive developers have only made patchwork solutions, ensuring temporary functionality. As these patchwork fixes keep snowballing, they inevitably create more and more constraints. Rebuilding such temporary solutions has no sense. In certain scenarios, the original software simply can't support the essential features. In others, introducing any enhancement becomes prohibitively expensive. These limitations become the company's new normal until they hit a critical impasse.

What are the typical breaking points?

1. A fresh look of a top manager as the legacy software impedes the business growth.

A newly appointed executive, business successor, or current manager may recognize the need for automation and cost-cutting. Why?

The top manager recognizes that the current software no longer offers the business a competitive edge. Questions arise: Why is the staff count so high? Why are we still using outdated tools like Access? Why can't tasks be done on mobile devices?

Upon closer examination, it becomes clear that the legacy software impedes efficient operations. Few employees grasp the intricacies of the business software ecosystem, reducing the company's competitiveness.

Realizing this, the top manager begins the search for a partner to modernize their software, ensuring it aligns with contemporary market demands.

2. The initiative of the head of department to lift barriers for their employees' daily operations.

As the client base expands, ideas for enhancements accumulate. Eventually, it becomes clear that the current software lacks compatibility with newer features, such as mobile access.

The need for experienced developers arises, prompting executives to assign them the task.

CHALLENGE

Addressing the cost estimation gap due to missing legacy software documentation and clear functionality understanding

The client has the software they want to modernize and their primary query is how much this will cost. To answer this, we first identify the best approach for modernization.

There are several modernization approaches to consider:

  • rewrite everything from scratch
  • integrate specific modules that tap into existing databases
  • develop new modules that complement the current system
  • OR even sometimes just simply support the current system

The manager starts searching for terms like "system modernization", "ERP modernization", "CRM modernization", or other queries (depending on the type of the business app). Through their search, they often discover experts like Belitsoft.

Upon reaching out to us, they typically share a brief overview of their challenges and objectives. In response, we probe with a series of questions to grasp the project's specifics.

To provide an approximate estimate of the app modernization cost, we ask a series of questions to find out the specifics of the project.

However, what happens if the client can't provide answers? They might possess outdated technical documentation, but such resources might not be reliable, especially if they depict functions no longer in use.

Without the details, any cost estimate is a shot in the dark. Clients who've sought estimates without the requisite documentation often encounter significant variances between vendors' quotes. One firm might quote $1 million, while another suggests $100,000, leaving the client bewildered by the vast difference.

We try to provide approximate figures based purely on our experience in the field. Still, there's a potential variance that could range from 1,000 to 5,000 hours.

To minimize this cost estimation gap, most vendors request technical documentation, which, unfortunately, is often absent.

So, how do we navigate such scenarios?

SOLUTION

Bridging the gaps with the discovery phase

Whatever modernization method the client prefers, the discovery phase is a must.

What do we do for you during a discovery phase?

  1. We sign the necessary documents (NDA, security, contract) to kick off the discovery phase with all the details cleared and secured in advance.
  2. Through meetings, we aim to comprehend the existing application. For this, we delve into the application, analyzing its functionality from both user and backend perspectives.
  3. Then, we analyze what the client wants in the new app and what the development team can do for the project. For that, we talk to the company stakeholder groups who work with this software. We gather feedback from users on which existing functions to retain and which to modify.
  4. We draw up all the required functionalities for modernization in a comprehensive document - Vision & Scope, detailing every aspect of the app modernization. We distill business ideas into technical language, ensuring clarity for developers. This foundational document will then serve as the basis for an accurate cost estimate.
  5. Based on the Vision & Scope document, we furnish detailed Optimistic and Pessimistic cost estimates.
  6. Should the client choose to proceed with Belitsoft for app modernization, we promptly provide a comprehensive project plan right after the cost estimation. This outlines the scope, goals, tasks, timelines, resources, and other pivotal project facets.

During my years of work, we've pitched in multiple modernization projects. So before the discovery, we can showcase sample documents and estimates to clients, if required, also provide references.

PROCESS

Breaking up the Discovery phase into transparent agile process

We explain our process to the client, shedding light on the rationale behind each step.

Structured Timeline. We segment the project into releases, further dividing these releases into sprints, which typically last 1-3 weeks.

Regular Demonstrations. At the conclusion of every sprint, we present a demo to our clients, gathering invaluable feedback.

Monitoring and Time Management. Throughout the project, we rigorously track both planned and actual hours spent. Time tracking is meticulous for both sprints and the project timeline. A detailed hour estimation accompanies the project plan.

Transparency through Reporting. After each sprint, the client gets a report on the hours spent and the explanation. This enables clients to assess if we are adhering to the initial timeline. The client decides the next steps based on actual data.

RESULT

Achieving an accurate cost estimate and minimizing risks

The Discovery phase significantly reduces the potential risk of underestimating or overestimating app modernization costs. While the cost estimation gap could be as wide as 100%, after the Discovery, can confidently narrow that down, providing you an accurate cost estimation with a possible 20% gap only.

To illustrate, consider a scenario where the initial fixed-price estimate is $50,000, but the actual cost escalates to $100,000. Such a situation presents a high risk of breaching the contract mid-project, especially if costs rise unexpectedly. Imagine the difficulty for both top managers and department heads in explaining to their superiors how a team was paid a $30,000 deposit but abandoned the project halfway.

The discovery phase eliminated this risk.

Clients benefit from the perspective of external professional consultants who bring a fresh pair of eyes. This external viewpoint is invaluable, especially when internal personnel might be resistant to change or suggest that adjustments are challenging or even impossible.

What comes next?

Typically, post-Discovery, our team is intimately familiar with the application. Having provided a competent estimate, we're primed and ready to kick off the app modernization, evidenced by these cases:

Contact us to get professional FREE consultation and give a fresh look to your business application.

Real-Life Client's Case:
Belitsoft Approach in Action

When a client comes to us, we follow all the described best practices and our time-tested approach to analyze the project, providing an accurate cost estimation and defining priorities for the development phase.

Client Background

A US-based company has been in the manufacturing market for a long time. Its owners are aware of software development processes in outsourcing, so they know quite well how to work with a remote team and set up transparent, effective communication.

Client's problem

For over 15 years, the client relied on their in-house custom CRM/ERP for order processing and production tracking, built on MSAccess + MySQL and Visual Basic.

Despite numerous updates over the years, the system, though functional, began showing signs of wear and glitches.

However, the client faced two critical risks that underscored the urgent need for application modernization.

  1. The imminent Windows update to version 11 might render the CRM/ERP non-functional.
  2. The system's legacy architecture hindered the incorporation of advanced modern features.

Proposed solution

The business owners envisioned a modern system, with web-based and mobile versions, tailored to their daily operational requirements.

Regarding technologies, the client was open to suggestions. From my experience with similar projects, there's a possibility to convert the current VB code to C# and retain essential business functions. This approach might save time and budget, but it depends on the clarity of the code. So the final decision should be taken during the Discovery phase together with the client.

Budget Considerations

I provided an initial budget range based on past engagements with similar systems. A more precise figure would be achievable post the MVP 1.0 phase priority setting. This involves mapping out essential functionalities for the new system and any potential additions for MVP 1.0.

The best way to get an accurate budget estimation is to start with a Discovery phase. To initiate this phase, I make a Discovery Proposal to the client. This is a structured guide detailing a project's background, objectives, scope, deliverables, timelines, and constraints. It outlines how the project will be implemented, using a Time & Materials (T&M) approach. This strategy emphasizes consistent budget tracking, expenditure reports, and periodic updates.

This transparency ensures the client is always informed, understands the progress, and can make decisions on any additional requirements or changes that arise. Ultimately, the Discovery phase minimizes potential budgeting discrepancies.

Key deliverables

During the Discovery, we deliver Visual & Scope (V&S) and Work Breakdown Structure (WBS) in about 60 hours.

After the Discovery, we provide a detailed cost estimation, accompanied by Statement of Work (SOW) for Discovery.

The next steps

Post-Discovery, equipped with a comprehensive understanding of the application, our team provides a precise cost estimate. With the client's approval, we then proceed with app modernization or custom development, as demonstrated in our past CRM/ERP projects:

Frequently Asked Questions

To expedite the discovery phase without sacrificing quality, we employ the following strategies:

  • Thorough Preparation. Before diving into the discovery session, we immerse ourselves in research. We gather extensive information about the project, delve into the client's industry, analyze competitors, and define user personas.
  • Time-tested process. Our discovery phase is guided by proven methodologies. Relying on our time-tested scenarios ensures we're always asking pertinent questions, ironing out crucial details, and thoroughly covering all project aspects. This approach ensures a comprehensive understanding without starting from scratch each time.
  • Client Collaboration. We strive to establish clear and swift communication with the client's stakeholders groups. This is especially true for individuals interacting with the current system and those who'll be engaged with the new one. Their insights streamline the discovery process and guide the system's enhancement.
  • Focused Prioritization. Not every detail needs to be fleshed out in the discovery phase. Instead, we concentrate on the project's most vital components, reserving more nuanced details for subsequent phases.
  • Gap reduction in cost estimation. The discovery phase aids in narrowing the gap in cost estimation for complex projects due to a clear understanding of the software's functionality.
  • Risk minimization. The discovery phase significantly reduces the risk of underestimating or overestimating the app modernization cost, ensuring that projects are not halted midway due to unforeseen expenses.
  • Gaining external insights. The discovery phase brings in external professional consultants who offer a fresh perspective, especially when internal personnel are resistant to change or find it challenging to adapt to new processes.
Never miss a post! Share it!

Written by
Business Development Director at Belitsoft
Expert in IT staff augmentation (5 dedicated development teams have been created, 500 team members have been hired).
5.0
1 review

Rate this article

Leave a comment
Your email address will not be published.

Recommended posts

Belitsoft Blog for Entrepreneurs
How Much Does a Custom Software Development Cost
How Much Does a Custom Software Development Cost
How to Calculate Software Development Cost: Our Detailed Estimation Process Every project brings unique challenges. Relying solely on the Ballpark Estimation often yields rough, risk-prone estimates. While quick, we steer clear of this method. Why? Our aim is to offer you precise estimations, ensuring you can plan your budget effectively and mitigate project risks. You can contact me directly right now to discuss your project. Step 1: Detailed Requirements Gathering Clear and well-defined requirements are the cornerstone of accurate project costing. Typically, we commence with 1 to 3 complimentary meetings. During these interactions our business analyst (BA) works closely with the customer to grasp the idea and its intended product outcome. From this collaborative dialogue, a Proposal for Discovery Phase, along with estimates, is prepared, highlighting its projected duration. Once the proposal receives approval, we launch the Discovery Phase. Depending on project complexity, this phase usually spans between 40 to 160 hours. Drawing from our vast experience, this timeframe ensures a thorough yet efficient process of gathering. The main goal during this stage is to define the project's scope in detail. The outcome of this effort is that our Business Analyst crafts Vision and Scope document, which sets the stage for accurate cost estimation. Example of a Vision and Scope document Following this, the Work Breakdown Structure (WBS) is created— a clear, structured table that serves as the blueprint for project cost estimation. An exemplar WBS table derived from the Vision and Scope Step 2: In-Depth Cost Estimation by Senior Specialists Upon gaining a comprehensive understanding of the product vision during the discovery phase, we transition to the cost estimation step led by a specialized team. This team functions like a SWAT unit, comprising senior-level experts. The core of such a SWAT team is a back-end developer with system architect experience and a front-end developer. Depending on the project's nuances, we may also involve a UX/UI designer, project manager, and business analyst. With the groundwork laid by the business analyst during the discovery phase, where the BA aids in risk mitigation, our SWAT team refines and finalizes the hours needed for each feature or piece of functionality. Their calculations draw from extensive experience with projects of similar complexity and scope. Though our methodology finds its origins in the three-point estimation from the Project Management Body of Knowledge (PMBOK guide), it’s been enhanced over nearly two decades of practical experience. We strive for a consistent 20% margin between optimistic and pessimistic cost projections. When risks are higher, this gap may expand. In such cases, we pair the optimistic value with a risk percentage, and the pessimistic value becomes their product. Whenever risks exceed our 20% target, we pinpoint the cause and suggest ways to mitigate it. Throughout this process, the project manager communicates with the client, spotlighting risks and presenting alternative trajectories. This collaborative approach ensures that clients remain informed and can make pivotal decisions with clarity. For clarity, here's a sample cost estimation by a front-end developer based on the WBS This meticulous approach to cost estimation extends to all specialists involved in the project. Step 3: Personal Client Demo To present the cost estimation results, Belitsoft team organizes a video call or a face-to-face meeting, depending on your location and preferences. This direct interaction lets us elucidate the reasoning behind every figure and discuss all associated risks. It also allows you to verify the expertise of our team and assess their grasp of your project. You're placed in the driver's seat from this point onwards. We prioritize clarity over complexity. Instead of inundating clients with intricate formulas, we ensure the entire cost estimation process is transparent and accessible. During the demo, we provide a consolidated table detailing rates and the final cost estimation. We incorporate an 'Agile coefficient,' set at 20%. This coefficient accounts for sprint planning, daily meetings, reporting, presenting demos, and incorporating your feedback. This approach guarantees you remain informed and actively involved, preventing any blind spots regarding the project's progress. The example of a final cost estimation table that includes hours, developers' rates, three-point estimation, and Agile coefficient Navigating High Cost Estimations If our cost projection seems steep, we usually recommend a phased development approach. The MVP Strategy The initiation with a Minimum Viable Product (MVP) is a beneficial method for startups and businesses. We help prioritize MVP features so that in a few months, you have a functional product to present to investors and gather initial user feedback. This approach not only aids in cost management but also provides valuable insights for further development. Learn more about MVP software development in our detailed post, where we explore feature selection and other essential considerations. Risk Management Our primary focus on risk management ensures final project cost aligns with initial optimistic estimates. This commitment reflects our dedication to transparency and trust. A Practical Scenario For instance, if tasked with developing a registration form with SMS-based two-factor authentication (2FA) and the client suggests an unfamiliar service provider with limited documentation, this raises potential risks. To address these, we propose: Switching to a more cost-effective email-based 2FA, generally more economical than its SMS counterpart. Using Twilio, a platform we're well-acquainted with, which offers comprehensive documentation. Both options are geared towards minimizing risks and delivering value. What You Receive at the Conclusion Comprehensive Documentation. Vision and Scope, as well as Work Breakdown Structure (WBS) documents, meticulously crafted in line with international best practices. Clear Estimations. A detailed breakdown of hours and corresponding USD rates for the project, coupled with a projected development timeline. Strategic Recommendations. Insights on segmenting the project into phases (MVP, 1.0, 2.0, etc.) for optimal execution. Technical Guidance. Expert advice on the ideal tech stack tailored to your project's unique demands. Team Composition. Proposals regarding the optimal size, scope, and roles of the delivery team for efficient project completion. Risk Management. Identification of potential risks, accompanied by actionable strategies to mitigate them. This ensures your budget and timeline remain consistent with initial projections. Our method ensures that its cost estimation will be both accurate and human-centric. Contact me to discuss your project.
Fixed vs. Time & Material vs. Cost Plus Pricing: Which is Better for Your Software Project?
Fixed vs. Time & Material vs. Cost Plus Pricing
In Belitsoft, we examine each case individually to choose the IT outsourcing pricing models that allow our clients to get real high-level skills on demand, decrease costs for development, and speed up the product delivery. In case you prefer talking to me directly, reach out to me now. What is a Time and Material Pricing Model I recommend a Time and Material in software development for: A startup with the expertise in IT; A medium or large business where decision makers have experience in managing staff remotely and understand how to work with offshore teams. Key features: What is a time and materials contract? Time & Material is a contract where the total cost isn't defined when the development starts. A software development company, which you hire, assigns specialists to your project at a fixed hourly or monthly rate. The final project cost is calculated de facto upon the number of hours spent by the assigned staff. You get freedom in changing project requirements and scope of work alongside the development. Typically, Time and Material pricing model is used in line with Agile project management methodology. The development process is iterative. Each iteration represents a full development cycle with an end result, for example, the delivery of a new feature or integration. Advantages of a Time and Material pricing model: ✅ You start the development quickly. Having detailed specifications isn't a must. Give the first task to the development team, and they'll start performing, while you're working on the next task; ✅ You pay only for the time spent de facto. You don't pay sick leaves or holidays, your vendor takes on this responsibility. On top of that, the agreed rate doesn't change during your cooperation, making budget planning easy; ✅ You can adjust the level of your managerial involvement. On the one side, you can limit your participation by weekly meeting and focus on other business tasks instead. Otherwise, you can fully control every development step directly or by assigning your Product owner or other representative. Anyway, you have regular meetings with a vendor's project manager, and get immediately notified in case of any urgent updates or issues. Disadvantages of a Time and Material pricing model: ❌ The cost of the project might differ from the initial estimates. In Time and Material pricing model, you are free to change or add requirements in the development process. However, in this case, you pay for the developers' time that hasn't been planned initially, and your budget grows. 👉 How does Belitsoft resolve it? You get a skilled Project Manager and Business Analyst (on demand) from us. They help you describe the project specifications in more detail before the development. The more details are specified, the better picture of the result you have, and the lower is the risk of spending time on wrong tasks. It allows you to add or change some details in advance. ❌ You may not know what specialists are behind your project. T&M is a result-centered model when you expect a certain result till deadline. Usually, you don't even know the team structure. As a result, there is a risk of quick turnover in the team, which negatively affects the team expertise in your product and may delay its delivery. 👉 How does Belitsoft resolve it? Belitsoft has introduced a best practice for Time and Materials contract in software development. Our clients personally interview and choose key specialists for their projects. Then, we take on the responsibility to retain them as long as your project requires. On top of that, a Project Manager from our side acts as an intermediary person who communicates your ideas to a development team, makes sure that your requirements are clear to them, solves any urgencies, and gives you regular updates. How we applied T&M in the real project: Client: the global creative technology company. Product: custom resource management software. Project highlights: The client needed a complex resource management system that was supposed to be scaled and upgraded in line with the enterprise growth. We opted for the Time and Material pricing model because: the client wanted to retain full control over the project; the development was gradual and continuous, the client needed the freedom of changing and adding tasks on the go. When the software was already in use by hundreds of employees in the enterprise, Belitsoft kept on improving it according to the growing company and employees' needs. To be exact, we automated a unique business workflow, migrated the software to the Cloud, and realized other improvements – all step by step without downtime for the client's company. Following the Agile project management technique, the software development process was iterative and flexible. When the client had new tasks, their product owner communicated with Belitsoft's project manager and business analyst to analyze and agree on details. After that, the team developed and delivered the results. Finally, the project manager received client's feedback and asked the team to make changes if needed – all in a quick turnaround. Now, the client successfully uses the software to automate resource management workflows. Thanks to this, the enterprise optimized working processes and the number of managers, reaching significant budget savings. What is a Cost Plus Pricing Model I recommend a Cost plus model in outsourcing for: A medium or large business, typically a product company, with an in-house development team. Usually, a company needs extra resources when their in-house staff is overloaded or when they lack the required expertise; A startup where a decision-maker has had a previous experience with outsourcing services. Key features: How does Cost plus pricing work? You have a long term project or a series of projects for 1+ year. You contact an outsourcing software development company to get a dedicated team of IT specialists, which is a cooperation model that goes ideally with Cost+. The members of a dedicated team are vendor's employees de jure, but they become your full- or part-time employees de facto with a fixed salary. You fully manage them as your in-house employees. How is price determined using Cost plus pricing? Selecting the Cost plus model in outsourcing, you take on a monthly payment that includes: the salary of hired IT specialists (with fees actual for the vendor's country) and the overhead to a vendor, which covers utilities, rent, insurance, and other expenses. With Cost+, you know what your monthly payment consists of and how the money is distributed, and you understand which specialists with what salary work for you. As for project management methodology, you can choose Agile, Kanban, Waterfall, or others depending on specifics of your tasks. Advantages of a Cost plus pricing strategy: ✅ You save about 40% of budget compared to development costs in the US, UK, Israel, etc. By outsourcing software development to the countries of Eastern Europe, you save money on developers' salaries and fees, without sacrificing the quality; ✅ You select each team member personally. Usually, a vendor's HR team pre-selects candidates for you. Then, you personally or your team interview the shortlisted ones and select those who meet your requirements; ✅ You are very likely to get a high-performance team. Typically, a dedicated team comprises specialists that have experience of working as a part of a dedicated team and perfectly know how it works (for example, they can work with communication and management tools, like Jira, Slack, etc). So, they start performing as a united team from day one, bringing you great outcomes. Disadvantages of a Cost plus pricing strategy: ❌ Your in-house staff may oppose hiring a dedicated team. Some managers and in-house developers turn out to be not able or not ready to accept and communicate with an offshore team. Partly, this happens due to the lack of such experience. However, for others, it's a job security issue, when employees may feel competition and doubt their skills and further employment. 👉 How does Belitsoft resolve it? Thanks to our years-long expertise in building dedicated teams for Cost+ contracts, we know how to create a team that will be on the same page with your in-house employees and managers. Our Project Manager will introduce communication and management tools, like Jira, Slack, Microsoft Teams, or others, and will help your in-house staff get the maximum benefit from them. As a result, the communication becomes smooth and friendly, and both teams start working as a single one. ❌ You take the same level of responsibility as with an in-house staff. You pay the salary, sick leaves, and holidays. Besides, you should provide constant workload for such a team, otherwise, you pay for downtime. 👉 How does Belitsoft resolve it? We flexibly react to the changing scope of work can scale up and down the dedicated team quickly. As for the expenses, you clearly see what the pricing includes, how expensive every specialist is, or which part of the budget goes to pay fees – you get access to employees' contracts and other financial documents. How we applied Cost+ model in the real project: Client: an Israeli high-tech company. Product: custom development, customization, and testing of network intelligence and security solutions. Project highlights: The company had a team of in-house developers and testers. However, due to the growing demand for customization of their products, the in-house team didn't cope with the workload, and the waiting list stretched for years. To deliver the products on time, the client decided to compensate the lack of in-house resources by partnering with Belitsoft. Initially, their request was to create a dedicated team of QA engineers. Later on, having evaluated the professional approach and results of Belitsoft's work, the enterprise entrusted the customization and then custom development of their products to us. We suggested and implemented communication and management tools for smooth and productive mutual work of the in-house and offshore teams. We also know how essential it is for large product enterprises to retain key specialists in a project due to knowledge domain specifics. For that, Belitsoft assigned an account manager who was 100% free for our client. His task was to retain key professionals in the team by timely forecasting and preventing any issue within the team or with the client. By following this best practice, we've retained 85% of the team for over 2 years up to now. As a result, our dedicated team has scaled up to 100 testers and developers on board, providing a definite increase in velocity. Belitsoft has helped attract new clients, increase revenue, and save 40% on development and testing. What is a Fixed Price Model I recommend a fixed price model for: A startup with a new idea but without experience in the IT industry; A small or medium-sized business with detailed specifications and clear goals; A medium or large business with a pilot project. Usually, a company describes project specifications in detail for apple-to-apple comparison among new vendors. Based on the results, they pick a vendor for further cooperation. Key features: A fixed price model is the contract based on a fixed project cost agreed before the work starts. You can use it when you know exactly what to do. All your requirements and specifications are described in detail, usually in a Statement of Work (SOW). Based on the SOW, a software development company evaluates the team size and a time frame and makes a budget assessment. Typically, a fixed price model is a go-to option for MVPs and small projects with limited budget and strictly determined deadlines. This outsourcing pricing model is traditionally used with Waterfall project management methodology, which is not an iterative approach. Your development team will break down the work into predefined chunks and deliver them according to the SOW. Choosing a fixed price model, you can expect that a development team will strictly follow the agreed specifications without ongoing changes. Advantages of a fixed pricing model: ✅ You know for sure what budget and results to expect. You get exactly what you've requested in the SOW with regard to the price, terms, and quality; ✅ You run very limited risks during the development process. Any project risks (technological, operational, or related to skill resources) become the responsibility of a software development company; ✅ You can compare vendors. You get an opportunity to compare several outsourcing companies by giving them a pilot project. Thus, you get insights about working with each of them and can decide which one suits to you best. Disadvantages of a fixed pricing model: ❌ You may face a high risk of wrong project assessment. Few businesses and startups have a clear vision of the end goals. As a result, the SOW poorly covers project details, often leading to wrong project assessment in terms of budget and deadline. If your project is underestimated, a vendor might lack time to complete it without sacrificing the quality. If it's overestimated, you pay more than your project really costs. 👉 How does Belitsoft resolve it? If you don't have a SOW, Belitsoft will assign a Business Analyst and a Project Manager who will do a project discovery phase for you and document all your requirements with detailed specifications. As a result, you get an exact final cost estimation. ❌ You cannot start the development right away. The well-though Discovery phase is a must for a fixed price model. Otherwise, your requirements might cause a bunch of issues (wrong choice of a tech stack, underestimation, difficulty to add certain features further, etc). So, you and your vendor require extra human resources, time, and money for the preparatory phase instead of starting the development right away. 👉 How does Belitsoft resolve it? We know that a skilled Project Manager and Business Analyst are a key to a thorough yet quick discovery phase and detailed specifications. Belitsoft has well-versed specialists with years of experience in fixed price projects who will take on this stage. ❌ You cannot make changes in the project on demand. The major difference between fixed price and time and material is that in a fixed price model, you cannot alter your initial project scope and requirements whenever you need it. 👉 How does Belitsoft resolve it? We suggest that you make change requests – formal proposals to alter a product. Thus, you get a possibility to add extra details to your initial Statement of Work, though it might require extra time and budget. How we applied a fixed price model in the real project: Client: the US-based health tech startup. Product: custom CRM for clinical trials. Project highlights: A fixed price model was selected as the startup founders came to Belitsoft with detailed requirements. The development team started from a discovery phase. Our business analyst and business development specialist elaborated a step-by-step development strategy that linked the client's requirements to their technical realization. It covered both business and technical details, such as market research, product features, tech stack, etc. As a result, the client received a precise cost estimation with a technically-backed vision and scope of the project and the exact deadline. We set up clear deadlines for every milestone and delivered results on time and on budget. We also applied change requests when the client wanted to change or add new deliverables. It took some time and money, but the client received the product that perfectly met the requirements and became competitive on the market. If you lack sufficient in-house resources or skills that are required for successful and timely project delivery, let's talk and resolve this challenge together.

Portfolio

Portfolio
Proof of concept for validating the Idea of Cloud-Based Virtual Fuel Cards for a Logistics Startup
Proof of concept for validating the Idea of Cloud-Based Virtual Fuel Cards for a Logistics Startup
We made Proof of Concept and Business Analysis to help the logistics startup validate the business idea of cloud-based virtual fuel cards before starting the full-scale development process.
Migration from .NET Framework to .NET Core and AngularJS to Angular for HealthTech Company
Migration from .NET Framework to .NET Core and AngularJS to Angular for HealthTech Company
Belitsoft migrated EHR software to .NET for the US-based Healthcare Technology Company with 150+ employees.
Azure Cloud Migration for a Global Creative Technology Company
Azure Cloud Migration for a Global Creative Technology Company
Belitsoft migrated to Azure the IT infrastructure around one of the core business applications of the global creative technology company.

Our Clients' Feedback

Any software development, programming, or design needs we have had, Belitsoft company has always been able to handle this for us

We have been working for over 10 years and they have become our long-term technology partner. Any software development, programming, or design needs we have had, Belitsoft company has always been able to handle this for us.

We are very happy with Belitsoft

Belitsoft has been the driving force behind several of our software development projects within the last few years. This company demonstrates high professionalism in their work approach. They have continuously proved to be ready to go the extra mile. We are very happy with Belitsoft, and in a position to strongly recommend them for software development and support as a most reliable and fully transparent partner focused on long term business relationships.

We can recommend Belitsoft and are looking forward to start a follow-up project

It was a great pleasure working with Belitsoft. Software Development Company. New requirements and adjustments were implemented fast and precisely. We can recommend Belitsoft and are looking forward to start a follow-up project.

Let's Talk Business
Do you have a software development project to implement? We have people to work on it. We will be glad to answer all your questions as well as estimate any project of yours. Use the form below to describe the project and we will get in touch with you within 1 business day.
Contact form
We will process your personal data as described in the privacy notice
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply
Contact us

USA +1 (917) 410-57-57
700 N Fairfax St Ste 614, Alexandria, VA, 22314 - 2040, United States

UK +44 (20) 3318-18-53
26/28 Hammersmith Grove, London W6 7HA

Poland +48 222 922 436
Warsaw, Poland, st. Elektoralna 13/103

Email us

[email protected]