Skip to content
OVERWRITE54

Custom software & apps

Software that simplifies everyday work.

I develop software and apps that bring tasks, information and people together. Whether you need business software, a web application or a mobile tool, the solution is shaped around your workflows and the systems you already use.

Discuss a software project Explore the focus areas
Concept exampleShared data. Views for each task.

When is a tailored solution useful?

  • Information from emails and spreadsheets has to be copied repeatedly.
  • It is hard to see who is responsible for each task and what is still outstanding.
  • You want to develop your own application or add features your current software lacks.

Possible applications

Your workflow. Your application.

A solution can start with a single workflow and expand as needed. Possible applications include bookings, project and membership management, reporting, quotation and product configurators, learning platforms and training administration. We clarify which features make sense for your project.

01

Business software & portals

CRM and ERP solutions, industry-specific applications and customer portals bring tasks and data together. We agree who can view, edit or approve information and which existing systems should be connected.

02

Mobile apps

Apps for iOS and Android make information and features available on the move, for customers or employees. We plan which devices to support and whether accounts, system integrations or notifications are needed.

03

SaaS & digital products

Would you like to offer software as your own product? Together, we define a useful first version. Features such as user management, separate customer data, subscriptions and integrations are shaped around your business model.

Concept example

Jobs in view. In the office and on the move.

A service business schedules visits in a spreadsheet, emails job details and receives updates by phone. The office often has to ask what has been completed. A shared application brings together each job, appointment and status. Employees can record their updates directly against the job.

  1. 01

    Plan the job

    The office records the customer, appointment and task, then assigns the visit to the responsible person.

  2. 02

    Send updates on the move

    Employees view their jobs on mobile devices and record what has been completed and which questions remain open.

  3. 03

    Keep track of progress

    The office sees the current status against each job and can plan the next steps without having to gather separate updates.

Working together

How your software takes shape.

The process depends on your project and what is already in place. We agree goals, initial features and how we will work together in advance. A clearly defined first version can be a useful starting point.

  1. 01

    Understand

    We discuss the task, the people who will use the software and your existing systems. This gives us the requirements and priorities.

  2. 02

    Agree the concept and interface

    I propose the features, structure and user interface. Your ideas and feedback inform our agreement before the planned implementation begins.

  3. 03

    Develop and test

    I develop the agreed features and test workflows, permissions and system integrations. We review progress as agreed so that feedback from your business can be taken into account.

  4. 04

    Introduce and develop further

    We plan rollout, handover and any ongoing support early on. At the end, I carry out the agreed steps. We can then plan further features to suit your needs.

Good to know

Questions about custom software

Key questions about features, existing systems and your first version.

What determines the work involved in my software?

The key factors are the tasks the software needs to support and the data and systems involved. Before preparing a proposal, we clarify:

  • Number and depth of workflows
  • User roles and permissions
  • Data structure and migration
  • Interfaces and external systems
  • Target platforms, tests and operational scope
  • Business rules for industry-specific applications
Is an idea enough, or do I need a concept already?

An initial idea or a description of a specific problem is enough for a conversation. Together, we clarify who will use the application and what it needs to do. If more detailed planning is needed first, we agree its scope in advance.

Can my existing software be extended?

That depends on its technical condition and the available access and rights. I first review the code, dependencies and documentation. We then discuss which extensions and integrations are feasible. Data imports and full system migrations are assessed separately.

Do I need an app, or would a web application be enough?

That depends on the users and features involved. Together, we assess whether browser access is sufficient or an iOS and Android app would be useful. We also plan any store publication and ongoing maintenance; the store operator decides whether to accept an app.

What happens if requirements change?

We discuss change requests together. I assess their effect on features, effort and timing. We agree how to proceed before any additional scope is implemented.

What do I receive at handover?

We agree the deliverables, access, documentation and guidance during project planning. Usage rights and the extent of any source-code handover are also recorded, distinguishing client-specific results from reusable technical components. Any ongoing support is agreed separately.

Your software idea

What should your software make possible?

Whether you have a product idea, a recurring task or an existing application, tell me what you want to achieve. Together, we can identify a sensible next step.

Discuss a software project