Custom software for daily operations.

Give your team a shared place to see work, make decisions, and update records. Marc Kubernus designs and builds internal software around the people and systems involved.

Discuss your project

Build an operational interface when your process needs one.

Possible projects include an admin portal for customer operations, a queue for reviewing incoming requests, or a dashboard that brings relevant records together. The purpose is to help staff complete work, with clear actions and reliable states beyond a read-only chart.

A spreadsheet can remain the right tool for a simple, flexible task. Custom software becomes worth considering when multiple users, permissions, validation, record history, or connected data make the current setup difficult to manage.

AethDesign is Marc’s independent freelance studio in Germany. Startups and small to midsized technology companies work with Marc remotely, from mapping the workflow through implementation and an agreed handoff.

Tools shaped around operational tasks

Admin portals and permissions

Provide controlled access to records and actions. Define roles, validation, confirmation for consequential changes, and useful activity history according to the scope.

Queues and shared work

Organize requests by status, priority, and owner. Include empty states, conflicts, exceptions, and recovery so staff can manage work beyond the happy path.

Dashboards and reporting

Combine agreed data sources with explicit metric definitions and freshness indicators. Support filters, drill-downs, or exports where they help a real decision.

Design around the task before building the screen

Start with a representative workflow, realistic data, and the roles that will use it.

  1. Understand

    Observe the current process and identify bottlenecks. Agree on users, data sources, access boundaries, and acceptance criteria.

  2. Design

    Map screens, actions, permissions, and exceptions. Review a focused prototype with the people who will use the tool.

  3. Build

    Connect the interface to the required data and services. Test role boundaries, core journeys, validation, and recoverable errors.

  4. Introduce

    Plan rollout, any agreed data migration, user guidance, and handoff. Define operating responsibilities and the process for future changes.

Typical deliverables

  • Workflow and permission model
  • Implemented operational interface and integrations
  • Relevant tests and acceptance evidence
  • Setup, usage, and handoff documentation

Questions and answers

When is existing SaaS a better choice?

When a product fits your workflow, access needs, and integration constraints, buying it may be more practical. Custom software is worth assessing when those constraints leave important work unsupported. Maintenance is part of that decision.

Can the tool work with our current systems?

Yes, where their APIs, data access, and permissions allow it. We review your stack first and decide which system remains the source of truth before introducing another interface.

What does ownership and handoff mean?

The project agreement defines delivered source code, accounts, access, documentation, and usage terms. Hosting, third-party licenses, data migration, and support are specified separately where relevant.

Who handles ongoing changes?

Your team can maintain the documented implementation, or continued development can be separately arranged. We agree who handles hosting, dependencies, backups, support, and requests for new features.