A guide for business owners and project teams
Prepare your project and discuss a software development proposal
Pricing is negotiable and discussed individually for each project. We agree the quote after reviewing the workflows, features, integrations, languages and ongoing support you need. A useful proposal explains the deliverables, assumptions and responsibilities of both teams. Use this guide to prepare that conversation and compare the work included in each offer.
By the Grevision team in Prishtina, KosovoStart with workflows and users
The cost follows the work needed to make the product useful, including the less visible parts behind the interface.
Define the first release
List the users, essential tasks and acceptance conditions. A booking application may need availability rules, permissions and notifications; a storefront may need product variants, a cart and order handling. Separate these essentials from later improvements.
Identify integration and migration work
Include existing APIs, data quality, access permissions and the information that must move into the new system. An undocumented integration or a large data cleanup can change the estimate, even when the screens look simple.
Compare proposals on the same basis
An estimate is easier to assess when deliverables, assumptions and responsibilities are visible.
Ask what is included
Compare design, development, testing, deployment, documentation and handover. Ask which tasks your team must complete, how feedback is handled and what happens when a requested feature changes the agreed scope.
Discuss the project price
The price is negotiable and depends on the project's agreed requirements. Discuss whether the proposal covers a defined scope, a discovery phase or development time, then agree milestones, acceptance and payment arrangements. Where requirements are still unclear, a focused discovery phase can establish a useful basis for the quote.
Plan the cost of operating the application
The development proposal and the running costs describe different parts of the same product.
Account for services and maintenance
Include hosting, domains, payment services, subscriptions, backups and monitoring where relevant. Clarify support hours, updates and how future improvements will be commissioned. Ask who owns the accounts and who pays recurring charges.
Bring a brief to the first conversation
Send the business goal, users, workflows, integrations, languages, budget range and target date. Grevision uses these details to discuss open questions and a suitable scope. Any price and delivery commitment belongs in the agreed project proposal.
Put the guide into practice
Turn a catering workflow into an estimate you can compare
A catering team wants orders, event dates, payment records and returnable dishes in one place. This sample brief turns that goal into work a supplier can estimate. Its features and checks are proposed requirements for a new project.
What to include in the first version
- Office staff create an order with its event date and customer details.
- A shared calendar reflects orders and approved date changes.
- Each order has linked payment records and a dish-return status.
How to check the work
- Change an event date: the order and calendar show the same new date.
- Record a payment: the linked order shows the matching amount.
- Record a partial dish return: the remaining quantity stays visible.
Questions for the proposal
Ask each supplier to identify whether online payment processing, spreadsheet migration and automated messages are included. Their integrations and data requirements affect the work. Pricing remains negotiable for the agreed project scope.
Compare the work behind three project types
Use these portfolio examples to discuss scope. They describe different deliverables, not fixed-price packages or equivalent estimates.
| Project type | Define for a first release | Questions that change the estimate | Project example |
|---|---|---|---|
| Multilingual website | Service pages, approved content languages, gallery and contact route. | Who supplies translations? How are content changes published? Does an existing site need redirects? | RA Plâtrerie Peinture |
| Operations software | One complete staff workflow, its users, data and acceptance criteria. | Which rules change orders or payments? What data must move? Which systems exchange information? | Te Lisi catering software |
| Web and mobile product | The first useful journey on each platform and the content or services they share. | Which platform launches first? Who supplies content? Which external services and store accounts are needed? | Mapsarch architecture platform |
Prepare your project enquiry
Choose what you already know, then describe the workflow in the form below. Your selections are included only when you send the enquiry.
Your enquiry outline
Project type: Business software Which connections need discussion? To be clarified Content languages to discuss: To be clarified Existing data: Not selected
Take a project brief to your next conversation
Download an editable brief with scope and supplier questions. Use it with your team, then send us the requirements you want to discuss.
Editable text file · No registration
Tell us about the first useful release
Add the users, the task they should complete and any deadline or constraint. We will use your outline to discuss scope and open questions.
Pricing is negotiable for each project. We agree the quote after discussing your requirements and the scope of work.
Prepare your project enquiry
info@grevision-ks.comDiscuss your software project with Grevision
We are a registered software development company in Prishtina. Send your brief so we can discuss requirements, open questions and a suitable next step.
Discuss your project