M
Matapps

We build websites, apps and client portals.

Offer

Comprehensive IT Services — from idea to launch

We help define the first sensible scope: website, client portal or MVP application.

Starting packages

Company website

For companies that need a new offer presentation, contact flow, and core pages.

This is not the right start if:

the first version already needs a complex system with login, roles, and many workflows.

  • Homepage and subpages
  • Offer sections and CTA
  • Contact form
  • Deployment and basic configuration
Timeline: from 2 weeks from PLN 4,500 net
Send a brief

Client portal

For companies that want to organize data, statuses, communication, or project handling.

This is not the right start if:

the internal process, data, or expected user actions are not clear yet.

  • Wireframes and working screens
  • Login and basic roles
  • Forms and statuses
  • API or backend integration
Timeline: from 4 weeks from PLN 9,000 net
Discuss scope

Application / MVP

For products that need a first working web or mobile version.

This is not the right start if:

the goal is a full product with every feature before defining a focused launch version.

  • Main user flow
  • Frontend and UI components
  • Backend and database
  • Deployment and next development plan
Timeline: from 6-8 weeks from PLN 18,000 net
Let’s talk

Which scope fits best?

ScopeBest starting point whenFirst outcome
Company website

the offer and contact path need to be clearer

a clear company presentation ready for sales conversations

Client portal

clients or teams need one shared workspace

statuses, data and communication in an organized view

MVP application

an idea or process needs to be tested with a working version

a first product with the core user flow

Common project scopes

Company website

Homepage, offer pages, contact, core CTA and implementation.

Client portal

Login, data views, statuses, forms and operational screens.

MVP application

A first product version with the main user flow.

What you receive after delivery

Delivered scope

Working screens or application in the agreed first-stage scope.

Code and configuration

The project remains in a repository with basic environment and deployment configuration.

Usage guidance

Short guidance for content, form, portal, or next-step management.

Development plan

A list of items worth improving in later stages without mixing them into the launch scope.

Common questions

What affects the estimate?

The estimate depends on the number of screens, complexity, integrations, content, and whether the project needs backend, admin panel, or mobile app work.

Can we start with a smaller scope?

Yes. It is often better to start with a base version that solves the key problem and move the remaining features to the next phase.

Can you work on an existing project?

Yes, if the codebase, repository access, and environment make it possible to assess the project safely before work begins.

How is scope creep controlled?

The work is split into stages and design decisions are confirmed before implementation. This makes time and budget easier to control.

Next step

Not sure which scope to start with?

Briefly describe the company, process and goal. This makes it easier to decide whether the right path is a website, client portal, MVP application or one of the products.

  • what problem should be organized
  • who will use the solution
  • whether there is a deadline or first phase