When orders, documents and approvals are scattered across spreadsheets and inboxes, it’s hard to tell what needs doing next. I build applications that bring the work into one place and connect it to the systems you already use.
I’m Marcus Biel. I’ll work with you to decide what the first release needs to do, design the application, and help build it.
Perhaps a spreadsheet that worked for two people now has several versions, or every handoff means searching through an email thread. The work has grown beyond the tools you started with.
A custom application can help when
people enter the same data several times or copy it between systems.
staff have to piece together information from emails, files and spreadsheets.
it’s difficult to see who is responsible, who approved something or how far a task has progressed.
an existing application forces people to use workarounds for important steps.
several teams rely on the same information but each maintains its own version.
I ask the people doing the work to walk me through it. Who does the work? What information do they need? Which decisions and exceptions matter? The answers define the scope.
What I can build for you
Internal business applications
An application for the everyday work of your business, from processing orders and managing cases to checking documents and organizing approvals.
I model the data, steps and responsibilities involved. User roles determine who can view, edit or approve information.
When your team outgrows a spreadsheet
When several people work with different versions of a file, a shared application can bring the data and the workflow together.
People can enter data, search records, check progress, and run reports in one place. I help you choose which fields, formulas, and records to bring over from your spreadsheets.
Sometimes one missing workflow forces people to leave an otherwise useful application.
I look at how it would fit into your systems, either as an extension of an existing application or as a separate component connected to it.
From a shared spreadsheet to a working order book
Several people update the same spreadsheet and agree on changes by email. Order 1042 has three line items and an attached quote, but no delivery date. Who can approve it, and which version of the file should they trust?
I walk through an order with the people who handle it. In this example, the workflow has five stages, with a clear line around what the first release will do.
Record the order.A team member enters the details or imports them from an existing system.
Check the details.The application flags missing details and checks for values that contradict each other.
Request approval.The person responsible reviews the order and approves it for the next step.
Track progress.Everyone involved can see the current status, supporting documents and next task.
Send the approved order.An integration sends the approved information to the next application.
The first release covers entry, validation and approval. For order 1042, the missing delivery date is visible before anyone signs off. Tracking subsequent work and passing approved data to another system can follow in a later release.
Start with a design or go straight to a first release
Bring the spreadsheet, a form, or a typical order to our first conversation. We can work from what your team uses today.
When the scope is still open
A written software design sets out the proposed workflow, essential features, connections and an initial estimate.
When the workflow is clear
I can estimate the work and build one complete workflow. Your staff can put test orders through it and check the required fields and approval rules. Before rollout, we agree which existing records to bring across and who will support the application.
What I learned building Maildroppa
I’ve worked with Java since 2001 and run my own software product, Maildroppa.
Small businesses use it to manage subscribers, send newsletters, and automate follow-up emails. I work on both the features customers see and the systems behind them.
Running a product has taught me how to choose a first release and make changes while customers are already using it.
The case study shows how the product works and which decisions went into building it.
I start by asking where things stand and what you want to achieve. Your examples show who is involved, which information they handle and where special rules apply.
I work with your team to prioritize the features. The first phase should support one clearly defined workflow from start to finish.
If the scope is still open, I can prepare a design and an estimate. You’ll see the workflow, the main features, and the systems the application needs to connect to.
If the scope is already clear, I can start building.
2. Build and review the application together
I develop the agreed features and regularly show you the latest working version.
You can try it on familiar tasks and tell me what needs to change. We’ll discuss how your feedback affects cost, timing, and scope.
The implementation covers the agreed screens, data processing, permissions, integrations and tests.
3. Prepare for rollout and ongoing use
Before rollout, I check the existing records and user accounts with your team and confirm where the application will run.
We also agree on the documentation and handover your team needs, who will support the application and how development will continue.
You work directly with me
I’m Marcus Biel. You’ll work directly with me on the design, and I’ll write code alongside the developers on your project.
I can join your team or bring in specialists as needed. Before we start, you’ll know who’s doing what and how we’ll stay in touch.
I’m based near Munich and work remotely across Germany. We meet regularly to try the software and make decisions about the next release.
For a first conversation, describe your situation and show me an example from everyday work. It could be a spreadsheet, a form or a typical request.
I’ll work out what else I need to prepare a proposal and whether it would help to start with a software design.
How do we decide whether to build custom software?
I look with your team at how much of the work existing products already cover and where your team still has to fill the gaps.
I check whether adapting your current software or adding an integration would be enough, or whether you need a separate application. Rollout, operations and future development all factor into the decision.
Can you integrate our existing systems?
I review the interfaces, data access and other technical options the systems provide.
Then we agree which data to transfer, which system owns it and what should happen when processing fails.