You have an idea.
Let’s talk.
An idea, a working prototype, or a product to improve. Describe who it is for and what needs to change; the scope, priorities, and next step can take shape from there.
[email protected] ↗Frequently Asked Questions
Find answers to common questions about our services.
What should I send to start a project?
Tell us what you want people to do, who the product is for and what already exists. A short description is enough to begin. We use the first conversation to clarify the problem, constraints and possible scope before preparing a proposal.
How do you estimate a project timeline?
We estimate after understanding the essential flows, integrations and dependencies. The proposal describes the work and the assumptions behind its schedule. Changes in scope or access to existing systems may affect that estimate.
How is the price established?
The price follows the agreed scope, technical requirements and delivery arrangement. We explain what the proposal includes and how changes would be handled so the commercial terms are clear before work begins.
When do we agree on payment?
Payment stages, invoicing details and available payment methods are agreed as part of the proposal. The arrangement should make clear what each stage covers and what is expected from both sides.
How do you choose the technology?
We start with the product, its existing systems and the people who will maintain it. Our work includes web and mobile applications, backend services and AI integrations. We explain the relevant technology choices in the proposal.
Can you work with an existing application?
Yes. We can review an existing codebase, connect an external service or develop a defined addition. We first inspect the relevant structure and constraints so the scope reflects the application as it is.
What happens after delivery?
We agree on handover, documentation and support responsibilities in the project scope. Continued development or maintenance can be planned separately. Support coverage and communication arrangements are written down rather than assumed.
What is the best way to reach you?
Send project inquiries to [email protected]. Include a short description and any relevant links; if timing matters, explain the constraint. For an existing project, we use the communication arrangements agreed for that work.
Are all your products used in the same way?
No. The collection includes hosted applications, software you can run on your own infrastructure, developer tools and mobile apps. Each product page explains its purpose and links to the relevant website, download or documentation.
What does an AI integration involve?
We can connect language models and related services to a product workflow, including assistants, retrieval and automation. The scope considers response quality, data handling, usage cost and error behaviour alongside the visible feature.
Can maintenance be an ongoing engagement?
Yes. Maintenance can cover agreed updates, bug fixes, performance observation and follow-up development. We define access, responsibilities and the work included in the arrangement according to the application.
How do you decide whether a project is a fit?
We look at the problem, scope, dependencies and the expertise the work requires. A clear first release or a well-defined improvement is a useful starting point. We discuss feasibility before committing to a delivery plan.