Guides: how to commission and accept software
Practical answers to the questions that come up before choosing a vendor: how to describe a project, what drives the cost, how to approach integrations and which cooperation model to choose.
Preparing a project
-
How to write a request for proposal for software
What to include, what to leave out and how to compare offers from software houses.
-
How to choose a software house: questions to ask before signing
What to check in their projects, what to ask before signing and which signs to worry about.
-
MVP: how to plan the first version of an app
How to choose the features of the first version, what not to cut and how to grow in stages.
-
Software house or an in-house IT team?
Three models compared, when to choose which and how to avoid vendor lock-in.
Costs and billing
-
How much does a mobile app cost and what drives the price
What changes the price of an app, the costs after launch and how to limit the budget.
-
Fixed price or time and materials? Billing models for IT projects
Fixed price or time and materials: how they work, when to use which and how to limit risk.
-
How to calculate the return on process automation
The cost of the current process, the payback period and benefits a spreadsheet does not show.
Technology and integrations
-
Comarch ERP integration: API, XML files or the database?
Official API, file exchange or the database - when to use which and what to watch.
-
Electronic document workflow: where to start
Choosing the first process, approval paths, ERP integration and common implementation mistakes.
-
Web app, mobile app or PWA - which to choose?
How they differ, what they cost to maintain and which one to choose for a business app.
-
Offline apps for field staff: how they work
Storing data on the device, syncing, conflicts, photos and security.
-
Process automation and AI in a company: where to start
Which processes to pick, where AI makes sense and where plain automation is enough.
Acceptance and further development
-
User acceptance testing (UAT) step by step
Who tests, scenarios, test data, reporting defects and the acceptance decision.
-
Taking over a software project from another vendor: how to do it safely
What to collect from the previous vendor, a code review and a takeover plan without downtime.
Let's talk about your project
Describe in a few sentences what you want to build or improve: an app, a platform, an integration or a process. We reply within one business day. The first call is an analysis, not a sales pitch.