Website · Real estate
Real estate
A German-language lead-generation site for a Zürich property brokerage: fixed-price selling, free valuations, listings and local landing pages.
Services / Web Applications
Web applications that carry real workloads.
Dashboards, portals, SaaS platforms and management systems: multi-role web applications built to be used all day, every day.
From our work: CutQ
01In practice
What this means in practice
A web application is software that happens to run in a browser. It has roles and permissions, data that must stay consistent, and users who expect it to be fast at nine in the morning when everyone logs in at once.
We design the information architecture first: who sees what, what they can change, and what happens next. Then we build it as a system with a proper backend, not a set of pages with forms attached.
Reporting, exports, audit trails and admin tooling are in the plan from the start, because they are what make an application usable by a business rather than a demo.
02What we build
Specific things we deliver
Admin dashboards
Live operational views with the controls to act on them.
Customer and partner portals
Self-service access to orders, documents, requests and status.
SaaS platforms
Multi-tenant products with accounts, plans and billing hooks.
Management systems
Bookings, cases, assets, projects: whatever your business has to track.
Reporting and analytics interfaces
Filters, charts and exports on top of trustworthy data.
Multi-role applications
Permissions designed in, not bolted on.
Lead-generation and qualification flows
Multi-step forms that branch by intent and land in your CRM with context.
Document and approval workflows
Uploads, review, sign-off and an audit trail.
03Where it fits
Situations that usually lead here
- 01
Customers or partners keep emailing for information they could look up themselves.
- 02
Your product idea needs a real multi-user application, not a prototype.
- 03
Managers want live numbers instead of month-end spreadsheets.
- 04
Several teams need the same data with different views and rights.
- 01
Discover
We map roles, data and the journeys each type of user takes.
- 02
Define
Information architecture, permissions model and integrations, priced against an agreed scope.
- 03
Design
Flows and screens designed per role and tested with real users.
- 04
Build
Backend, frontend and admin built together, released weekly to a demo environment.
- 05
Launch and support
Production deployment, monitoring and a plan for what comes next.
07FAQ
Questions about web applications
If people log in, have roles, and change data, it is an application. If the job is to inform and convert visitors, it is a website. Many projects need both, and we build them as one system when that is the case.
Yes. Every application we build is designed for phone screens as well as desktops, because that is where much of the daily use happens.
Roles and permissions are designed during planning, not added later. We use established authentication approaches and keep an audit trail of who changed what.
We design for real network conditions: small payloads, sensible caching and clear feedback when something is loading or has failed.
Start here
Have a problem worth solving?
Tell us what you're trying to build, automate or improve. We'll help you figure out the right technology and the best way to build it.