Customer portals, dashboards and internal tools
A customer portal where your clients log in, a dashboard with the numbers that matter, or an internal tool that replaces spreadsheets and copy-paste. I develop web applications like these around the way your company works.
I'm all in on AI, so I develop much faster than before. I stay careful with permissions and data, because these tools hold your customers' and your company's information. I work with companies without their own developer and with teams that need more experience on board.
I usually reply within one working day.
What I develop
Web applications for your customers and your team.
Customer and client portals
Customers log in, see their orders, documents, bookings or reports, and change their own settings. Your team gets fewer emails and calls.
Dashboards and reports
Charts and tables with the numbers your team needs, with filters, Excel and PDF exports, and reports that run in the background.
Admin panels
The screens your team uses to manage products, customers and content. I make them easy enough that nobody has to ask a developer.
Custom CRM and ERP tools
When standard software doesn't fit your process, a smaller tool of your own often works better. For customers, orders, stock, pricing or production rules.
Roles and permissions
Who can see and change what, for staff, customers and partners. Also separate data per customer when many companies use the same system.
Connections to your other systems
Accounting, CRM, payment providers, booking systems and email, so nobody types the same data in twice.
How I work
You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.
I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.
AI-first, with me in charge
Claude Code, Codex and my own agent workflows write much of the code for forms, tables and screens. I decide how the tool works and check every change, above all permissions and data handling.
I stay in control
AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.
The way you want to work
Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.
I think like an owner
I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.
Ways to work with me
Fixed price, a flat monthly rate, or hourly. It's always me doing the work, not an agency. If you're not sure, describe what you need and I'll suggest one.
Examples of my work
Portals, dashboards and admin tools I have developed.
Reports and certificates in a large learning platform
A flexible reporting system with filters, configurable columns and exports, plus certificate workflows, inside a large Laravel LMS. I turned customer conversations into requirements the team could build on.
Visitor portal and admin tools
Visitors register, plan their visit and get QR tickets. The organizer scans tickets at the door and has event statistics and admin tools. AI suggests relevant exhibitors to each visitor.
Workflows, triggers and reports
Users set up financial workflows, watch market data and get AI-generated reports when something important changes. With credits, Stripe billing and background jobs.
What clients say
"He worked on performance optimization, customer-specific features, and a major custom reporting system."
"He then built exactly what was needed and kept us informed throughout."
"You have a chat, you express what you need, and he comes back with what you asked for."
Questions
Why not use standard software?
Often you should, and then I tell you. A custom tool makes sense when your process is what sets you apart, or when the standard tool needs so many workarounds that people avoid it.
Can the portal use data from our existing systems?
Yes. If your CRM, accounting or ERP has an API, the portal can read from it and write back to it.
Can customers only see their own data?
Yes. Permissions and separate data per customer are part of every portal I develop.
Which technology do you use?
Usually Laravel with Vue, and often Filament for admin panels. If your team already works with another stack, I use that.
Can we start small?
Yes. A first version with the most important screens often shows whether the tool helps. Then we add what is missing.
How do you charge?
Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.
Get a quote
Who will use the tool, what they need to do in it, and what you use today. A few sentences are enough. I'll reply with what I would develop and what it would cost.
If you would rather talk first, book a 30-minute call or email contact@vincentschmalbach.com.