Before starting with MTeam
Before any technical work we describe the task and the requirements for the end result. You pay only for features that serve the business goal.
Discovery & specs
Clear documentation makes requirements unambiguous, removes rework caused by misunderstandings and lowers the cost of development.
Get an estimate
Pricefrom €3,000
01 / discovery & specs
When you need it
For working with another contractor
If you decide to work with a different team, we help you describe the task and requirements properly and minimize your risks.
For running a tender
A tender needs an independent, objective task description and requirements. We prepare documentation for a fair and objective tender.
02 / discovery & specs
What is included
UX prototype of interface screens
UX prototypes make the future product easy to use and feature-complete before any code is written.
Software architecture design
Architecture sets performance, reliability, and other technical traits of the product. We fit it to your load, budget, and team.
Technical specification
The specification distils all requirements for the UX prototypes, the software architecture and the project as a whole.
03 / discovery & specs
UX prototyping
Best-practice analysis
Researching the market and existing products helps you avoid common mistakes.
Screen design
Every screen gets a simple, clear and, most importantly, useful purpose for the end user.
Prototype testing and finalization
The draft is tested for gaps and optimization opportunities; the prototype is updated accordingly.
04 / discovery & specs
Architecture design
Technology stack
Technologies affect the speed and cost of development as well as the capabilities and limits of the product. We choose based on the tasks, needs and resources of the business.
Databases and their structure
The right databases and a well-designed storage structure define convenience, speed, integrity and security of data.
Core business-logic architecture
Almost every system has a core responsible for the main business logic. Its architecture defines overall performance, server requirements and security.
Microservice architecture
A microservice is an isolated mini-application solving a single task — usually one with special resource or security requirements.
System diagram
The result of architecture design: the links between the core application, microservices, databases and external services.
Operations scheme
How the product is run from the server-environment perspective: scaling, security measures and other important aspects.
The technical specification is written based on all of the above.
how we work
No surprises. Not in scope, not in the invoice.
- 01
Discovery call
We dig into the business goal, users and constraints — free of charge.
- 02
Fixed estimate
The team estimates every task with planning poker. The price is fixed for the agreed scope: if we underestimate, that’s on us. New requests are estimated separately.
- 03
Build in the open
A shared Slack channel, regular demos and progress you can see — no black box.
- 04
Launch & run
We ship to production and stay on call 24/7 — or hand over cleanly to your team.