IT & automation
Digital systems for your team
I help choose suitable software and build a tech stack your team can use in its everyday work.
Project example
Tirava: from choosing a route to sending an inquiry
The multilingual booking flow connects the service, route and required details with one central inquiry intake.
The project connects a multilingual service offer with route selection and inquiry intake.
Explore the project
A technical foundation for your team
Suitable tools can help your team handle inquiries and orders as systematically as a larger business. We choose systems that fit your budget and daily work. Your team tests the first implementation with real tasks.
- Pricing
- Project scope and price based on existing workflows and tools
- Timing
- Timing follows the agreed scope, available material and approval process.
Before work begins, you receive a proposal with a clear scope and costs.
Choose software for everyday work
Tools need to cover your tasks and work together. Selection also accounts for implementation effort, recurring costs and future maintenance.
Example system setup
Each tool has a defined role
An illustrative setup. Tool selection follows your requirements and the available budget.
Example details
- Website
- Explain the offer and capture the inquiry
- Customer records
- Maintain contact details, ownership and progress
- Connection
- Transfer the required details and report failures
Compare existing software with custom development
For a common task, we first assess suitable products already available. Custom development becomes an option when an important requirement cannot be met that way. Recurring fees, data migration and future maintenance also belong in the comparison.
Plan the tech stack as a connected system
We establish where customer data is maintained and how the website, customer records and other tools use it. I check available interfaces and export options. Your team should understand which system owns each task and where to make changes.
Extend an existing system where it makes sense
If your tools already support the work, a missing connection may be the main obstacle. I check that option before planning the effort of replacing a system.
Connect data and interfacesYour system setup
- Tool selection and system setup
- We assess which software fits your tasks and budget. I recommend a coordinated tech stack and handle the agreed setup, incorporating useful existing systems.
- Inquiries and customer status
- Forms capture the required details. Suitable customer records show status, next steps and ownership.
- Email automation
- Acknowledgements, internal notifications, reminders and approved reply templates support the workflow. Domain email connections are checked within the agreed scope.
- Data and interfaces
- Required fields, existing data sources and suitable APIs are identified. Transfers receive clear rules and handling for typical failures.
- Operation and handover
- Access, ownership and technical checks are documented. Updates, monitoring, corrections and improvements are agreed as part of the support arrangement.
Delivery and handover
Assess needs and tools
We review an actual workflow and the software already in place. This identifies which systems you need and which connections are missing.
Set up the systems
I configure and connect the agreed tools. Custom features are developed where the workflow requires them.
Test with your team
Your team tests the setup with realistic tasks and typical failures. At handover, I document accounts and the agreed responsibilities.
Before commissioning
Does this fit my business?
This suits businesses building a technical foundation or extending their existing setup. We can start with software selection or develop the tools and workflows you already use.
The recurring task can be explained with real examples.
Access and ownership can be clarified.
A subject-matter contact can review workflows and results.
What do I need to provide?
A description of the current workflow with sanitised examples
Access and documentation for affected tools
Decisions on data, responsibilities and permitted actions
What is agreed separately?
Available data and suitable interfaces are checked before committing to implementation.
Licences, hosting and third-party usage costs are listed separately.
Support scope, availability and response times are expressly agreed.
Automation performs only agreed actions. AI-generated replies and sensitive or consequential actions require human approval before sending or execution.
Do all existing tools need to be replaced?
No. We first assess which tools can be retained and which connection is missing. Replacement is proposed only as a specifically justified option.
Can we start with a small automation?
Yes. A bounded workflow such as acknowledgement, internal notification and follow-up can be a useful starting point. Scope and price depend on the tools already in place.
What happens after handover?
Ownership and the required support are clarified in advance. Technical maintenance and active improvement are different services with an explicitly agreed scope.
Can you help us choose new software?
Yes. We establish what your team needs and which tools are already in place. I compare suitable options with regard to ongoing costs and integration. Selecting and setting up your tech stack can be commissioned as a project on its own.
Which systems does your business need?
Tell me what your team needs to do and which tools are already in place. We can discuss selecting suitable software or extending your existing setup.