Responsibility within a business
As a manager in a medium-sized company, I led an ERP rollout, from reviewing processes to involving employees.
AsertionCompany
Building your software.
As part of your team.
We develop software for the processes your business depends on - together with your people and in your systems.
Management
One point of contact, from start to finish
I know software projects from both perspectives: as the person responsible within a business and as a developer.
We first clarify how your team works, which rules matter and where changes will help. You discuss priorities, effort and open questions directly with me.
I accompany your project from the first conversation through to the working system.
Background
From user to developer
Experience of an ERP rollout on the customer side still shapes how we plan and support projects.
In the business
2020
Founding the company
Since then, we have built software around business workflows, involving the people who use it every day.
Today
Asertion and ElbDesk
We develop custom applications, integrations and ElbDesk, the foundation we build on. Depending on the project, we use ElbDesk or develop standalone.
Your team helps shape the rollout
New software changes established habits. Business decisions and feedback from daily work are therefore part of implementation.
Make decisions concrete
We discuss actual cases, show examples and document the agreed business rules.
Try it before switching
Your employees test the application with typical tasks. Feedback informs the next stage; training and transition are part of the plan.
Partnership
How you work with us
Tobias Kietzmann is your point of contact. For each stage, we agree who makes business decisions, who contributes and how results are approved.
Clear responsibilities
You know who to contact with questions and which decisions are needed from your side.
Regular progress reviews
We show progress using actual workflows so your business teams can give feedback early.
Defined stages
Scope and effort are described before commissioning. You decide on further steps on that basis.
Handover and operation
Clearly agreed.
Beyond the rollout.
The project includes clear agreements on source code, usage rights, documentation, data export and access. For ElbDesk, we distinguish the existing foundation from customisations for your business. The scope is documented before commissioning.
Before commissioning
What we agree together
- Source code and rights
- Scope of handover and agreed usage
- Data
- Export formats and data transfer procedures
- Documentation
- Business rules, operation and key decisions
- Access
- Responsibility for accounts and permissions
Working together
From the first conversation to a running system
Every stage ends with a result you decide on.
First conversation
We talk about where you stand, where the bottlenecks are and what you expect. You do not have to prepare anything.
Result
A shared picture of the situation
Assessment
We tell you whether we are the right people, where we would start and what that first step costs. What the whole implementation costs only becomes clear with the concept.
Result
A recommendation for the first step
First stage
We set out one manageable first step: what belongs to it, who is involved and what comes out at the end.
Result
Proposal and schedule
Delivery and operation
We develop the solution, introduce it and stay on hand afterwards - for operation, for changes and for the next project.
Result
A running system with a dedicated contact
Contact
Where do things jam in your business?
Briefly describe the task and how it runs today. We discuss how we can help and what a sensible next step would be.
Send an enquiry
Tell us briefly where things are stuck. We will get back to you personally.
Thank you, your message has arrived. We will reply personally to discuss the next step.
A short description is enough. We will work out the details together.