Excel is the hub
One file has become important, but nobody knows exactly which version is correct anymore.
0:00 / ~0:00
Software Development
When your business touches the same data twice every day.
I build small, robust software solutions, automations and interfaces that fit your workflow exactly. No bigger than necessary, but clean enough that you can rely on them.
Typical symptoms
The problem is rarely the single spreadsheet. It is the workflow around it.
When work moves between files, inboxes, exports and gut feeling, a small targeted software building block is often worthwhile.
Data gets copied
The same information is moved manually through several systems.
Errors appear late
Checks only happen after something has already gone wrong.
Tools do not talk
An export here, an import there, but no robust connection in between.
Preparing quotes faster
Situation: Prices, variants and customer data were spread across several files.
Solution: A small tool brings inputs, templates and export together.
Result: Fewer copy errors and a clean draft ready sooner.
Interface instead of duplicate entry
Situation: Data was exported from one system and entered manually into the next.
Solution: A scheduled import checks fields, flags exceptions and logs errors.
Result: Routine work runs in the background while special cases stay controllable.
Overview for recurring work
Situation: Tasks were spread across inboxes, chat and spreadsheets.
Solution: A lean web view shows status, responsibility and next action.
Result: Fewer follow-up questions, clearer priorities and better handovers.
Managing Outlook signatures centrally
Situation: Email signatures were managed manually by employees. Different HTML and RTF formats created an inconsistent appearance.
Solution: A custom tool formats signatures centrally and creates them semi-automatically for rollout.
Result: Consistent signatures across the company, including links and images without making them appear as attachments.
Connecting an online shop to Galaxus
Situation: Products were managed through a shop CMS or Excel, but the platform had no native Galaxus plugin.
Solution: Registration and coordination with Galaxus were handled. A small backend tool creates Excel exports and connects the Galaxus interface via FTP.
Result: Smaller online shops can offer their products on Switzerland's largest marketplace without major infrastructure.
Backtesting trading strategies
Situation: A trader wanted to implement and backtest a strategy in TradingView but could not program it himself.
Solution: Different strategies were developed together, implemented with parameters in Pine Script and backtested extensively.
Result: Even an individual hobby trader can test algorithmic trading without expensive infrastructure or complicated bots.
The small first step
Understand first, then build.
The start is deliberately manageable. This quickly shows whether an automation, an interface or an internal tool will actually bring the best benefit.
- 1
Review the workflow
We look at the current work together: where do waiting time, errors, duplicate entry or media breaks occur?
- 2
Narrow the benefit
I suggest a first solution that stays small enough while still making a noticeable difference.
- 3
Build a prototype
You see early how the solution feels before too much time goes into details.
- 4
Hand over something stable
The solution is documented, tested and explained so everyday use does not depend on gut feeling.
Technology, but purpose-led
The stack follows the problem.
Depending on the task, this can involve web interfaces, databases, APIs, scheduled scripts, file imports, exports, permissions, logging, hosting or maintenance. What matters is not a trendy stack, but a solution you understand and can keep operating.
- Databases and clean data models
- APIs, interfaces and import/export
- Lean web tools for internal workflows
- Automations, logs and maintenance
Next step
Bring one concrete workflow that annoys you.
In the first call, we clarify whether a small tool, an automation, an interface or a clean analysis should come first.