Custom software and web applications for SMEs
Weber Development builds web applications, portals, dashboards and internal tools for SMEs in Eastern Switzerland, for when off-the-shelf software or Excel no longer does the job. Everything is developed in Bichwil SG by Seya Weber, with no agency in between. You get a tool that follows your workflow, and one person to talk to who wrote the code.
Last updated:
01
Who this is for
Businesses whose workflow currently runs on Excel, email and word of mouth. Typical situations:
- An Excel file has become the central database. Several people work in it, and nobody knows which version is right.
- Customers, members or property owners phone for information they could look up in a portal.
- Figures from two or three systems are copied by hand into a monthly overview.
- An older tool still runs, but nobody can change it, or the vendor is dropping it.
- Standard software covers most of the job; the rest costs time every day in workarounds.
Industries: manufacturing and trades, service businesses, property and condominium management, clubs and associations.
02
What is included
- Requirements gathering with the people who will use the tool daily, not only management
- Workflow sketch and a clickable prototype before any production code is written
- Development of the web application: TypeScript, React and Next.js for the interface, C# and .NET where an existing Windows environment calls for it, Postgres or SQL Server as the database
- Login, roles and permissions (who sees and edits what)
- Data import from Excel or the legacy system, checked for completeness
- Integration with existing systems via APIs
- Hosting set-up and backups
- Documentation and onboarding for users
- Optional: maintenance and further development after launch
03
How it works
- 01First call You describe the workflow that causes trouble; I ask where time and errors are lost. About 30 to 45 minutes, free of charge.
- 02Requirements and quote One or two conversations with the users, then a written quote with scope, stages and price. Typically 1 to 2 weeks.
- 03Prototype A clickable version using your real terminology and sample data. Typically 2 to 4 weeks.
- 04Development in stages Every two weeks a version you can try out; feedback flows straight into the next stage.
- 05Launch Data migration, training, go-live, support during the first weeks.
- 06Operation Maintenance agreement or handover to your IT, as you prefer.
04
What it costs
Two models, depending on how clear the scope is:
Fixed price with a defined scope and milestones. Fits once the prototype has settled what will be built; you know the price before the start.
Time and materials with a monthly report. Fits when the scope is deliberately left open or grows over time.
Running costs for hosting and maintenance are listed separately.
05
References
STWEG Roessliwiese
Self-initiated project for the Rössliwiese condominium owners' association in Bichwil: a public website plus a secure owner portal with document storage, news, events and role-based administration, login via email allowlist, deployed in the EU region.
WebGuide
Self-initiated bilingual knowledge platform with a searchable wiki and a built-in ticket system (attachments, email routing, spam protection) that turns repeated one-to-one PC help into self-service.
07
Frequently asked questions
Is custom software worth it for a small company at all?
If a workflow costs time every day or regularly produces errors, usually yes. The maths is simple: hours per week lost to Excel, retyping and follow-ups, times hourly cost, against the quote. We work that out together in the first call. If the numbers speak against a custom build, I say so and recommend a standard product.
What happens if you are unavailable or close the business?
A fair question for a one-person business. The protection is ordinary technology: widely used languages and frameworks (TypeScript, React, .NET, SQL), code and documentation in your possession, hosting on your own accounts.
Can we start with a small part?
Yes, that is the usual route. The prototype covers the one workflow that disrupts daily work most; once it proves itself, the next step follows. The first investment stays manageable.
How much time do we need to put in ourselves?
Most of it at the start: conversations with the users and feedback on the prototype. After that, a short meeting every two weeks and testing the interim versions.
Start a conversation