The IT contractor market is wide: from freelancers to software houses with several hundred employees. The difference in price and quality can be enormous, and a mistake most often costs rewriting the project from scratch. Below are the questions worth asking before you sign a contract, the red flags and the points that should go into the contract.
In short
- Demand working projects from the last year and the names of the people who will write the code.
- The contract must regulate scope, deadlines, rights to the code and maintenance terms.
- A price without a requirements analysis is a warning sign, not a bargain.
- Compare the total cost (rollout plus maintenance), not just the starting price.
Five questions you must ask
- “Show us 3 working projects from the last year.” This means websites and applications available on the internet, not mockups or graphic files. Ask what exactly the team that will make you the offer did on them.
- “Who exactly will work on my project?” In large agencies a senior often sells and a junior works. Ask for names, roles and who is responsible for code quality.
- “What happens if the project is delayed?” Delays happen. A good company builds a buffer into its estimate, reports progress every week and writes into the contract who bears the cost of scope changes.
- “What happens to the code after the project ends?” Ask about copyright, access to the repository and the ability to change contractors.
- “How much does maintenance cost?” Hosting, domain, updates, backups, fixes. Require these costs to be itemized in the offer.
The one-question test
Ask: "Why are you proposing this particular technology, and what happens if in two years I want to develop it elsewhere?". A reliable contractor will answer in plain language and point to alternatives.
Red flags
- No portfolio of working projects, or only screenshots.
- A price given without a conversation about requirements and without analysis.
- "We will do it in WordPress" as the answer to every problem, including a system with business logic.
- No contract, or a contract without deadlines, scope and acceptance rules.
- No answer on which technology will be used and why.
- A price several times lower than the rest of the offers (see how much a website costs in 2026).
Free consultation
Have an offer from another contractor? We will review it
We will go through the scope, technology and contract clauses and tell you what is missing. No obligations.
Book a call+48 731 377 999What the contract should contain
| Clause | Why it matters |
|---|---|
| Scope and schedule with milestones | Reduces disputes over what is included in the price |
| Transfer of copyright (economic rights) or a licence | Lets you develop the code with another contractor |
| Handover of the repository and access after acceptance | Protects you from dependence on one company |
| Acceptance rules and a warranty period for bugs | You know who fixes defects and how fast |
| Maintenance costs and SLA | You avoid the surprise of expensive hosting |
| Confidentiality and data protection (GDPR) | Required when the system processes customer data |
Discuss the legal details with a lawyer, especially for larger systems. The list above is a set of points to agree on, not a contract template.
How to compare offers
Write down your requirements
One page: project goal, key features, integrations, deadline and budget.
Collect 2-3 offers
Send the same description to every contractor so the offers are comparable.
Hold a technical conversation
Ask for a justification of the technology and a description of the project's risks.
Start with a pilot stage
For a larger system, order an analysis or the first module before you sign the whole thing.
Put the offers in one table: scope, technologies, deadline, rollout price, annual maintenance cost, rights to the code. Only then does it become visible that the cheaper offer often leaves out hosting, SEO, training or fixes after acceptance. Indicative ranges for websites are in the price list, and when planning a project with a grant, the article on FEPZ and KPO grants for business digitalisation will help (FEPZ: European Funds for West Pomerania; KPO: National Recovery Plan).
If you are looking for a local contractor, also see website development in Szczecinek and the project basics in the guide a business website in 2026.
Project acceptance and the first months
- Before acceptance, check the project on a phone and a computer and measure speed in PageSpeed Insights.
- Take over the repository, hosting and domain access, and the rollout documentation.
- Agree who responds to bugs after acceptance and how quickly (warranty and SLA).
- Plan backups and updates, and for larger systems also technical care (IT support).
How we work at Mikamait
You have direct contact with the people who write the code. You see progress every week, and after acceptance you get the rights to the code and the access credentials. We set up hosting, but you control the server. We explain every technology decision in plain language. Who we are and how we work is described on the about us page.
Need help?
Let us talk about your IT project
As a local software house from Szczecinek, we focus on transparent contracts, a fixed price and direct contact with the developer. We reply within 24 hours.
Write to us (reply within 24 h)Call: +48 731 377 999