Process
How we work: from discovery to launch and beyond
Every Sensaria project runs through the same seven steps, whether it is a company website, a SaaS product or a CRM integration. Each step ends with something you can review and keep, so decisions rest on documents and working software rather than on promises.
- Step 01
Discovery
We learn how the business works today: who the users are, which systems hold the data, where time is lost and what a good result looks like in six months. Short workshops with the people who do the work, plus a review of your existing tools and accounts.
- Step 02
Analysis & Architecture
We turn the scope into a technical plan: data model, integrations, hosting and security requirements. Risky parts, such as an old ERP interface or a data migration, get tested early with a small prototype.
- Step 03
UX/UI
We design screens, flows and content structure from real content, not placeholder text. Designs are reviewed on desktop and mobile and checked against accessibility basics before development starts.
- Step 04
Development
We build in short iterations on a staging environment you can open at any time. Code is typed, reviewed and covered by automated tests, and integrations are built against the agreed API contract.
- Step 05
QA
Before anything goes live we test it: functional tests against the scope, responsive layouts on real devices, cross-browser checks, performance budgets and a security review of authentication, input handling and secrets.
- Step 06
Launch
We deploy to production following a written runbook, set up analytics and error monitoring, and map redirects so existing pages and links keep working. Launch day is planned, not improvised.
- Step 07
Growth & Support
After launch the work continues where the data points: fixes and improvements, new automations, content and SEO/GEO work. Support runs as a monthly arrangement or as separate phases, whichever fits your budget.
Fixed-scope phases or ongoing work?
Both, depending on the goal. A new website, a first product version or a CRM integration runs best as a fixed-scope phase with a price agreed after discovery. Continuous work such as new automations, content, SEO and GEO runs best as an ongoing arrangement with a monthly plan. Many projects start with one and move to the other after launch.
| Model | When it fits | How it is priced |
|---|---|---|
| Discovery only | You need a plan, an estimate or a second opinion before deciding | Fixed price for the discovery phase |
| Fixed-scope phase | A clear result: a website, a product version, an integration | Fixed price per phase, agreed after discovery |
| Ongoing work | Improvements, automation, content, SEO and GEO after launch | Monthly arrangement, planned and reported each month |
How do we communicate during a project?
You have one contact person at Sensaria who is responsible for the project from the first call to launch. Every iteration ends with a short written update: what was done, what is next, which decisions are open. The staging environment shows the current state at any time, so you never have to wait for a demo to see progress. Workshops run by video call, with in-person sessions where they help.
Which languages do we work in?
English, Italian, German and French. Workshops, specifications and documentation follow the language of your team, and multilingual websites are written natively in each language rather than run through a translation tool at the end.
Who owns the code?
You do. The repository sits in an account your company controls or is transferred at handover. Domains, hosting, analytics and third-party services are registered to your company, not to us. If you ever change supplier, you take everything with you.
What documentation do you receive?
Enough for another team to take over without calling us:
- a README that explains how to run, test and deploy the project,
- the architecture and data model, with the reasons behind key decisions,
- API documentation, as an OpenAPI document where the project has a public or internal API,
- a runbook for deployments, backups and common incidents,
- a short guide for the people who edit content or manage the system day to day.
Where does the software run?
We choose hosting by what the data requires, not by habit. We have deployed on Vercel, Hetzner Cloud, AWS and Fly.io, usually behind Nginx with Let’s Encrypt certificates, and we containerize applications with Docker. When personal data is involved, we plan the data flows around the revised Swiss Federal Act on Data Protection (FADP) and the GDPR, and host in Switzerland or the EU where that is the right call. The full stack is on our technology page.
What happens after launch?
The system keeps running, and someone has to own it. We monitor errors and uptime, apply security updates and fix what breaks. We also keep improving what the data shows matters: a form that loses people, an automation that could save another hour a week, content that could answer more of your customers’ questions. If you prefer to run it yourself, we hand over and stay available for questions.
Ready to start? Describe your project on the quote page.
FAQ
Frequently asked questions
How long does a typical project take?
It depends on scope, integrations and how fast decisions are made. A focused company website is usually a matter of weeks; a first SaaS version or a custom internal system usually takes a few months. Discovery ends with a written timeline for your project, broken into phases with a deliverable at the end of each one.
Do you work at a fixed price?
Yes, for phases with a clear scope. After discovery we propose a fixed price per phase, or an estimate with its assumptions spelled out where the scope is still open. Ongoing work such as improvements, SEO or content runs on a monthly arrangement agreed in advance.
Who owns the source code and the accounts?
You do. The code lives in a repository your company controls or is transferred to you at handover, and domains, hosting and third-party accounts are registered in your company's name. Open-source libraries in the project stay under their own licenses.
Can you take over an existing website or software project?
Yes. We start with a review of the code, the infrastructure and the documentation, then give you a written assessment: what can stay, what needs fixing first and what it would take to continue. You decide after reading it.
Where will our application be hosted?
Where the data and the budget require. Marketing websites often run on a global hosting platform; applications that process personal or sensitive data can run on servers in Switzerland or the EU. We package applications with Docker so the hosting decision can change later without a rewrite.
What do you need from us during the project?
One person who can make decisions, access to the systems we integrate with, content or the people who own it, and feedback on each iteration within the agreed time. Most delays in software projects come from waiting, so we agree these points in the proposal.
Tell us about your project
A Swiss technology company in Lugano.