How we work
Custom builds are quoted for the agreed scope. No preset project price and no compulsory discovery package for a small, well-defined brief.
Tell us what needs to change, who will use it and which systems are involved. We discuss the goals, constraints and fit.
Where requirements are uncertain, agree a separate discovery scope. A prototype or technical proof of concept is included only if explicitly agreed—not an automatic MVP.
Deliverables, assumptions, acceptance criteria, timeline, responsibilities and payment milestones are written down. Hosting and email inclusions are itemised.
Review working software and progress at the agreed cadence. Scope changes are documented with their effect on cost and timing before work proceeds.
Agree deployment, documentation, code and account access. Support scope and hours are defined; ongoing hosting, provider charges and further development are identified separately.
Our existing terms cover defects against agreed acceptance criteria for 60 days after final acceptance. Ongoing application maintenance, new development and hosting operations are separate scopes. The signed agreement governs your engagement.
Read the existing termsWe can take an agreed engineering scope alongside your design or delivery team. The proposal defines who manages requirements, reviews work, communicates with the end client and owns the handover. Working-hour overlap is agreed during scoping; no fixed US coverage is advertised.
From application to operation
12 months of managed hosting included for eligible development projects, within agreed resource limits. Business email setup is included within the agreed first-year package.
We select the provider, region and architecture for the workload. European or US-region deployment can be scoped where the provider and project support it. Monitoring, maintenance and backup arrangements are defined before launch.
An agreed number of employee mailboxes, storage, aliases and shared addresses where supported. Setup covers MX, SPF, DKIM and DMARC, secure access and MFA where available, using a managed provider agreed in the proposal.
The proposal defines eligibility, the start of the 12 months, environments, compute, storage, traffic, mailbox limits, support hours, response terms, backups and restores, extra usage, renewal pricing and handover. Application maintenance and new features are separate from hosting operations.
GPU compute, intensive AI inference, large-scale video and unusually high traffic are quoted separately. External APIs, SMS, payment fees, transactional email allowances and paid email licences are itemised separately unless expressly included.
Your domain stays yours. Client access, data exports, migration and any provider or licensing dependencies are documented. Email migration is scoped separately where needed.
Included services and limits are confirmed in your proposal; hosting and email terms must be agreed before service starts.
Discuss your build and launchBefore we talk
A business platform, booking or service marketplace, connected web and mobile application, or SaaS product with meaningful workflows and integrations. We also work with software and design agencies on a defined engineering scope.
We quote after understanding the scope, integrations, operating requirements and delivery responsibilities. The proposal sets deliverables and payment milestones. There are no published build prices.
Only where it will resolve uncertainty. A clear, bounded project can move straight to a proposal. Discovery is scoped separately; it does not automatically include an MVP.
Eligible projects can include 12 months of managed hosting and business email setup within proposal-defined limits. Resources, provider, region, support, backups, mailbox allowances, start date and renewal costs must be agreed. Third-party and extra usage charges are identified separately.
Yes, enquiries from US businesses and agencies are welcome. Grundlabs is operated from Schwerte, Germany. We agree communication times and working-hour overlap for the project. Deployment close to US users can be scoped where supported; we do not advertise a US office or round-the-clock service.
The published terms transfer custom work after full payment, with third-party and pre-existing components retaining their licence conditions. The proposal specifies documentation, account and infrastructure access, export and migration arrangements and any dependencies.
No. They are our own products. Their current status is stated individually; working software and public product pages are not presented as evidence of market adoption.
Start with the problem you want to solve
A short brief is enough to start. Tell us about your users, the workflow and what a useful first release would change.