How it works
Four steps, each with a gate you control.
This is the whole engagement, from the first call to the handover, including the parts that decide whether you should go ahead at all. Nothing on this page turns up later as a surprise. The proposal repeats it, and the agreement makes it binding.
The call
Thirty minutes, free, on video. It starts from what you want to achieve, more revenue, lower cost or less risk, and then looks at the work standing in the way.
- Before the call, a short look at your company and the tools it visibly runs, so the time goes on your situation rather than on introductions.
- During it: why you booked, what you are trying to reach, and where the hours go today.
- At the end, a first idea of what a solution would look like, and a straight answer if this is not work worth doing.
The proposal
Within days, in writing, and yours to keep whether or not you go ahead.
- Where you are today: the points identified together on the call, and what each one means for the organisation.
- The solution: each component, how it works in practice, and what it changes for the team.
- Scope: the deliverables, with documentation and a handover session always included, and what is not included.
- A timeline in business days, one fixed price, and the possible next steps that came up but are not part of this job.
- Valid for thirty days. Accepting it means signing the services agreement that follows it.
The project
Map, build, test, hand over. You approve the design before anything is built and the result before it goes live.
- Map: a process walkthrough with your team, access set up, and the design confirmed in writing.
- Build: the components from the proposal, in your own accounts wherever the tool allows it.
- Test: on your real data, with corrections and your review.
- Hand over: documentation, a sixty-minute handover session with your team, and the transfer of every workflow, credential and access right.
- If something slips, usually while waiting on access, data or feedback, you hear about it straight away, with the consequences and a new date.
Afterwards
The system is yours. Support exists as a choice.
- What was built becomes your property once the final payment is made, with the workflows, the documentation and the credentials in your hands.
- Your team runs it. When something breaks, the documentation says what each workflow does and how, so you can look inside instead of phoning.
- Management and continuous improvement is available as a separate, optional arrangement: monitoring, fixes when your tools change, and a step further every month.
The terms, in plain words
The terms, in plain words
The proposal states these and the services agreement makes them binding. They are the same for every client.
- Fixed price
- One price for the whole job, agreed before work starts. Anything beyond the scope is quoted separately and agreed in writing before work on it begins.
- Payment
- Half at signing, paid online, which is what starts the work. The balance once you have accepted the delivered work, invoiced with fourteen days to pay. Amounts in Swiss francs, excluding VAT.
- Ownership
- What is built becomes your property on full payment. No licence from us to renew, and nothing that stops working if we are not around.
- Licences
- Third-party software is billed to you directly by its provider and stays in your name.
- Data and confidentiality
- The agreement covers confidentiality and the processing of personal data. Every system and service the work touches is named in the proposal, and every credential is handed over at the end.
- Timeline
- Projects are scoped in weeks, not months. The clock starts once the deposit is in and access is set up, and a delay on either side is named the day it appears.
What is needed from you
What is needed from you
- Access to the systems involved.
- Sample data to build and test with.
- One named contact person.
- Feedback within two working days at each review point.
Questions owners ask before they book
Questions owners ask before they book
- What does a project cost?
- A fixed price, stated in the proposal before anything starts, next to the scope it covers. There is no hourly billing and no retainer. Because scope and price are fixed together, a project is sized to what is worth doing, not to what could be built.
- How long does it take?
- Weeks, not months. The proposal gives the timeline in business days for mapping, building, testing and handover. It starts once the deposit is received and access is set up, and the most common cause of delay is waiting on access, data or feedback.
- Do we have to replace our tools?
- No. The work connects the tools you have and fills the gaps between them. Where a tool is missing, an existing product is preferred over a custom build. Replacing something is only ever a recommendation, and you make the call.
- Where does our data go?
- Every system and service involved is named in the proposal, and the services agreement covers confidentiality and the processing of personal data. Third-party services are contracted in your name, and every credential is handed over at the end.
- Will we depend on you afterwards?
- No. You receive the workflows, the documentation and the credentials, and your team is walked through them in a handover session. Support and continuous improvement exist as an optional arrangement, not as a condition for the system to keep running.
- What happens when something breaks?
- The documentation says what each workflow does and how it works, so your team can look inside. If you would rather not, the optional support arrangement covers monitoring and fixes, including when one of your tools changes.
- Do you use AI?
- Where it earns its place. A writing pipeline uses it to draft from your own knowledge base, with a separate step that checks every figure against that base and your approval before anything is published. A shareholder meeting moved from paper to digital with no AI at all. The starting point is the work, not the technology.
- What if the work turns out not to be worth automating?
- Then you hear that on the call or in the proposal. Some work should be removed rather than automated, and some should be done with a product you can buy. Saying so before quoting is the point of the sorting step.
- How do we start?
- Book the thirty-minute call and bring the one thing that keeps landing back on your desk. Nothing needs preparing.
Want to start at step one?
Book the call