FAQ
Questions we hear most often.
We've gathered answers to questions about working with us, costs, technologies and AI. Don't see your question? Write to us - we'll be happy to answer.
Working together
3 questions
What does working with you look like?
We start with a free consultation. We talk about your business, your users, how you work today and the results you want to achieve. Based on that, we propose a solution and the next steps. If the project needs a more detailed analysis, we agree its scope before we begin.
Next, we prepare a feature plan, a quote and a timeline. We design how the app looks and works, and once the direction is agreed, we move on to development. We work in stages, show progress regularly and gather your feedback. You can try out new features while the work is still under way.
On our side, we bring together design, development and deployment skills. On yours, we mainly need knowledge of your company, feedback and decisions by the agreed dates. You don't need to be technical. We explain the options available and help you assess their impact on the budget, the timeline and how the product works.
The path to launch ends with testing, deployment and handover of the solution. After that, we can take care of its maintenance and further development.
Do you sign NDAs?
Yes. Confidentiality is a standard part of our Cooperation Agreement, alongside scope, deadlines, warranty and the transfer of copyright. If you'd like to sign a separate NDA before discussing the details of your project, mention it in your enquiry.
Will you take over a project from another software house?
Yes. We start with an analysis: we review the code, infrastructure and documentation, and then tell you plainly what can be developed further and what needs fixing. We carry out further development in weekly sprints, with a plan, a quote and a deadline before we start.
Costs and timelines
3 questions
How much does an app cost?
We build apps from PLN 29,000. The final cost depends on what the system needs to do, who will use it and which tools it needs to connect to. The quote is shaped by, among other things, the number and complexity of features, the interface design, integrations and whether the app is to run in the browser, on phones or on both.
You don't need to come with a ready-made specification. It's enough to describe the idea or the problem you want to solve. We'll help you set priorities and separate the features needed at launch from those that can be added later. This way, the budget for the first version focuses on what will actually let you start selling, serve customers or improve how you work.
Before work begins, we agree the scope, the billing model and the timeline. We also outline the expected costs of maintenance and third-party services, such as hosting, paid integrations or AI models. You know what you're paying for and what it will cost to keep the product running.
How long does it take?
The timeline depends on the project scope, the complexity of integrations and how ready the materials are. It also matters whether we're building a new product, developing an existing app or automating a specific process. That's why we prepare the schedule once we know the requirements, broken down into stages and dependencies.
For new products, we often recommend starting with an MVP, a first version with the features essential for real use of the app. This lets you get the product to users sooner, gather feedback and test your business assumptions before investing in further modules.
You don't wait until the end of the project to see results. As we work, we present new elements and make them available for review. If you have a specific launch date, tell us at the start. We'll check what scope can be responsibly planned for that date.
How do you bill a project?
The price depends on scope, not hours, and you get a plan, a quote and a deadline before we start. We bill projects on a Fixed Price basis (milestones and deadlines set out in the contract) or on Time & Material when the scope needs to stay flexible. Development and maintenance after launch are billed monthly.
Technologies
3 questions
Which platforms do you build apps for?
We build web apps that run in the browser, and mobile apps for iOS and Android. Among other things, we build SaaS platforms, B2B portals and dashboards, CRM and ERP systems, product configurators, customer apps and tools for teams' day-to-day work. We also deliver online stores and business process automations.
One product can combine several parts, for example a mobile app for customers, a web dashboard for staff and a shared database. We handle both the part users see and the system logic, integrations and the environment needed to run it.
We choose the technology based on how the product will be used, the features it needs, the budget and your plans for growth. We'll help you decide whether an app running in the phone's browser is enough to start with, or whether you need an app installed from the App Store or Google Play.
Will you connect the app to our systems?
Yes. We connect apps to CRM and ERP systems, online stores, accounting software, payment providers, marketing tools and other services your company uses. The goal is a smooth flow of data and less manual copying of information between systems.
For example, an order from your online store can automatically reach your order handling system, a website form can create a contact in your CRM, and a document sent by a customer can trigger the right process. We tailor the scope of integrations to how your team actually works.
Before quoting, we review the documentation, available APIs, permissions and vendor limitations. We agree what data is to be sent, in which direction and how often. If a system has no API, we look at other options, such as file exchange or automating selected tasks. We confirm that an integration is possible after a technical review.
Which technologies do you work with?
We choose the technology to fit the problem, not the other way round. We build frontends in React, Next.js, Vue and TypeScript, mobile apps in React Native, Flutter, Swift and Kotlin, and backends in Node.js, PHP / Laravel and Python. We run infrastructure on AWS, Google Cloud and Docker, and implement AI with OpenAI and Claude.
AI
2 questions
Do you use AI?
Yes. We implement AI in apps and business processes when it helps solve a specific problem: shorten handling times, organise information, reduce manual work or make the product easier to use.
Among other things, we build assistants that draw on your company knowledge base, and solutions for reading and organising documents, classifying messages, drafting replies and finding information. We connect AI models to your company's apps and tools, including in automations built on n8n and Make.
We start by defining the task, the input data and how the results will be evaluated. We choose the model and decide which actions can run automatically and which need human approval. Along the way, we take into account usage costs, data access and the possibility of incorrect answers.
We also use AI in our own software development process. It helps us with analysis, coding and testing, while our team remains responsible for reviewing and for the quality of the solution we deliver.
Is my data safe in AI implementations?
Yes. During the analysis stage we determine what data goes to the model and choose a solution to match its sensitivity: OpenAI, Claude or an open-source model in your own system. The same rules apply as in every project: encryption (SSL/TLS), GDPR compliance and confidentiality set out in the contract.
Maintenance
2 questions
What happens after launch?
After the app goes live, you get 3 months of warranty support on the terms set out in the contract. During this period, we fix bugs covered by the warranty. New features and changes beyond the agreed scope are planned as further product development.
We can also look after the app on an ongoing basis under an SLA package. Depending on the agreed scope, it includes 24/7 monitoring, server maintenance, security updates and handling of support requests. Support hours, priorities and response times are set out in the contract and matched to how important the system is to your business.
After launch, we can develop the product based on user feedback, usage data and your business goals. If your IT team is to take over maintenance or further work, we agree the handover of the code, documentation and necessary access.
Can we keep developing the product together after launch?
Yes. After launch, a dedicated team develops and maintains the product: we deliver new features in sprints, while monitoring, updates and 24/7 SLA support run in the background. Whenever you want, we'll hand the product over to your IT team.
Write HELLO, and we'll take care of the rest.
Describe in two sentences what your app should do. We'll reply with a concrete plan, quote and deadline, with no obligation.
- Transparent pricing, apps from PLN 29,000
- Weekly sprints
- 3-month warranty and 24/7 SLA