Call
Thirty minutes on what the software must do and what it replaces.
I'm Ilyas, a developer who builds web apps and internal tools for small companies. I write the front end and the back end, test the parts that matter, and stay on after launch to fix what comes up.
Client names are left out. Each entry says what the software does and what my part was.
Memberships, class booking and a check-in screen at the front desk, built to run on a tablet.
Daily orders from five shops in one place, with a print-ready bake list each morning.
A small service that keeps rooms, prices and cancellations matched between two systems.
Shifts, swaps and reminders for about two hundred volunteers, with a simple admin view.
An open-source helper for reading messy dates typed by people, with a long test suite.
Monthly reports that used to take two days of copying, now generated overnight.
Sample projects. Replace them with your own work, code links and images.
The software I am proudest of is the kind nobody notices, because it just works every morning.
Five bakeries placed their daily orders in one shared spreadsheet, and one wrong paste could empty a shelf.
The brief: Keep the way the shops order, remove the copying, and print a bake list for the kitchen by 4 AM.
Sample case study. Replace the story, steps and images with your own project.
Where I have worked, most recent first.
Work is split into short phases, each with a demo and a fixed price.
Thirty minutes on what the software must do and what it replaces.
A written plan with phases, prices and what is out of scope.
Weekly demos on a test site you can click through yourself.
Go live, a handover session, then support if you want it.
| Option | What it covers | From |
|---|---|---|
| Code review | A written review of an existing app with a list of fixes | $1,200 |
| Prototype | A working first version of one feature in two weeks | $4,800 |
| Build phase | Four to six weeks of development with weekly demos | $12,000 |
| Support plan | Updates, fixes and a monthly health check | $600 a month |
| Day rate | Pairing with your team or short fixes | $700 |
Sample content. Replace the options and prices with your own.
I write the code myself. For bigger projects I bring in people I have worked with for years.
My projects work best when I can talk to the people who will use the software every day.
Typed front-end code · Server rendering · Relational databases · Background jobs · Payments · File uploads · Search · Automated tests · Accessibility checks · Cloud hosting · Monitoring and alerts · Data exports
Yes. The code, the documentation and the hosting accounts are yours from day one.
Usually. Tell me what you have on the first call and I will say honestly if it is a fit.
For simple tools, yes. For customer-facing products I work with a designer.
Two weeks of fixes are included. After that, a support plan or a day rate.
Yes, which is why client names are not on this page.
A fixed price per phase, agreed in writing before work starts.
Tell me a little about the project. I reply within two working days with times for a call.
hello@ilyasbrandvold.example
That is usually where a good project starts. Send me a note.