Skip to content
Services

Custom Software with .NET — Leave the Excel Chaos Behind

Custom software is software built exactly for the way your business works — instead of forcing your workflows into an off-the-shelf product. Yurtbay.dev builds tailored business applications, integrations and APIs with C#, ASP.NET Core and Blazor for small and medium-sized businesses, based in Recklinghausen, Germany — robust, secure and maintainable, from requirements to day-to-day operations, all from one person.

When does custom software pay off for an SME?

Not always — and I'll tell you so. Custom software pays off when recurring workflows eat time every day: when the same data is typed in several times, when an Excel file serves as the "database" for orders, stock or planning, when several isolated tools don't talk to each other, or when standard software only half-fits after expensive customisation. Then your own application pays for itself through the hours saved — week after week. If, on the other hand, an off-the-shelf product covers your case well, that's what I'll recommend.

How do we replace the Excel and Access chaos?

The typical picture: one central Excel file nobody can work on at the same time, versions like "final_v7_NEW" circulating by email, macros only one colleague understands — or an Access database nobody has dared to touch for years. Replacing it is a classic custom-software project with a clear scope: a small business app with a real database (Microsoft SQL Server) your team works in simultaneously, with user permissions, required fields instead of typos, and traceable changes. Your existing data is migrated — and an Excel export naturally remains available, for reporting and your accountant.

What does custom software cost? The honest answer: these factors decide

Nobody can quote a serious price without knowing the scope. What actually drives the cost:

We clarify these questions in the intro call — after that you get a firm quote instead of hourly-rate surprises. And you don't have to start with a big project: often the best route is a first, clearly scoped module that solves the biggest pain point.

Why .NET and C#?

.NET is the Microsoft standard for business applications — and therefore the natural choice for businesses already running Windows, Microsoft 365 and SQL Server. For you that means: predictable support cycles thanks to LTS releases instead of framework-hopping, a huge developer base instead of dependence on an exotic technology, and applications that run on your server, in the cloud or in a container. With ASP.NET Core and Blazor you get modern web applications your team uses in the browser — with nothing to install on each workstation.

How the development works — in 4 steps

  1. Intro call (no obligation): You describe the workflow that costs time today — I'll tell you honestly whether custom software is the right route or an off-the-shelf product will do.
  2. Concept & firm quote: We define the scope together; you receive a concept with a firm quote instead of hourly-rate surprises.
  3. Implementation in stages: You see a usable version early and give feedback before details are set in stone — no months of radio silence until a "big handover".
  4. Operations & evolution: Hosting, updates and extensions after go-live — if you like, as ongoing care through the IT support packages.

A developer who understands your business

You talk directly to the developer who builds your application — no project-manager telephone game, no junior learning on your production system. That also means no overengineering: you get exactly the software your workflow needs — not the most expensive framework showcase. And if AI features such as document processing belong in the application, both come from one person — see AI consulting.

Frequently asked questions about custom software

What does custom software cost for a small business?

It depends on the scope: the number of processes and screens, integrations with existing systems, data migration from Excel or legacy systems, reporting needs, and where the application runs. We clarify exactly these factors in a no-obligation intro call — after that you get a firm quote instead of hourly-rate surprises. Often you deliberately start with a small first module.

When is standard software the better choice?

When an established product covers your case well without expensive customisation — for example for accounting or standard processes. Custom software pays off where your workflow is what sets you apart, or where standard products only fit with contortions. You'll get that assessment honestly in the intro call — even if it turns out to be "buy, don't build".

How long does development take?

That depends on the scope: a clearly defined first module — say, replacing one central Excel list — is ready far sooner than a full ERP-style system. A realistic timeline is always part of the firm quote, and because implementation happens in stages, you work with a usable version early on.

What happens to our existing Excel or Access data?

It comes along: I migrate existing data from Excel, Access or legacy systems into a proper database (Microsoft SQL Server), cleaning up the usual legacy issues such as duplicates and formatting errors along the way. An Excel export remains available — for reporting and your accountant.

Can we start small and extend later?

Yes — that's actually the recommended route. We start with the module that solves the biggest pain point and then extend the application step by step. That keeps the risk small, and every expansion stage is based on real usage experience instead of a spec written at the drawing board.

Who maintains the software after go-live?

I do — the same person who built it. Hosting, updates to current .NET versions, backups and further development can be covered as ongoing care through the IT support packages. But you're not locked in: the application is built with widespread standard technologies that any .NET developer can maintain.

Further reading: .NET know-how from the blog

Discuss your project — no obligation