Freelance
A developer for your team. The technical details.
This page is for people who develop themselves or lead a team: which projects I am right for, what I work with, and how I secure changes before they go live.
Which projects I am right for.
A good fit
- Web apps: dashboards, portals, internal tools
- Interfaces where design and usability matter
- Company websites, also in several languages
- Web3 frontends: wallets, live data, dashboards
- Automation: connecting systems and their APIs
Also possible
- The backend an app needs: APIs, login, integrations
- Command-line tools
- Taking over and tidying up existing code
Not my field
- Mobile apps for the app stores
- Windows software
- Running servers, specialised database work
What I work with
Interface
- TypeScriptTypeScript
- ReactReact
- Next.jsNext.js
- Vue.jsVue.js
- Tailwind CSSTailwind CSS
Behind it
- Node.jsNode.js
- REST APIsREST APIs
- PostgreSQLPostgreSQL
- Headless CMSHeadless CMS
Web3 and systems
- SoliditySolidity
- RustRust
Delivery
- Automated testsAutomated tests
- DockerDocker
- CI/CDCI/CD
What teams book me for. Two typical cases.
An experienced developer who joins your project.
You have a product and more work than your team can handle. I work on agreed days of the week on what is next on your list: new features, the interface, or the parts nobody gets around to.
What you get
- Web apps, dashboards, customer portals and internal tools
- Interfaces with attention to design and usability
- Web3 frontends: wallet connection, live data, dashboards
- Small tools and automation for recurring work
How it runs
What it costs
How you get to a price
- 1A call, about 20 minutesYou tell me what you need.
- 2A written estimateYou see the estimated hours and what they include.
- 3You approve a budgetI bill the hours actually used and tell you early if it will not be enough.
For orientation
100 EUR per hour, booked by the month
You book fixed days of the week for one month at a time. I bill the hours I actually worked. All prices net.
A week to look at your app and fix what is most urgent.
The app works, but bugs come back and small changes take longer than they should. I take a week to go through the code, fix what I can in that time and write down what I would do next.
What you get
- An honest assessment: what is solid and what is fragile
- Automated tests for the most important parts
- The most urgent problems fixed, as far as a week allows
- A written list of next steps, in plain language
How it runs
What it costs
How you get to a price
- 1A call, about 20 minutesYou tell me what you need.
- 2A written estimateYou see the estimated hours and what they include.
- 3You approve a budgetI bill the hours actually used and tell you early if it will not be enough.
For orientation
3,500 EUR for one fixed week
The scope is one week of my time, 35 hours. A week does not fix everything: if I see in the first call that it will not be enough to be useful, I tell you. All prices net.
What happens before a change goes live.
Software is connected: a change in one place can break another. I secure what I build with automated tests, and every change has to pass them before it is released. This is what such a run looks like.
Simulate a change in
A change comes in
Something is changed in Orders. Before it can go live, the whole project is checked automatically.
A test fails, the release is blocked
The change broke something in a different place. It is caught here, on my side, and nothing reaches your users.
Fixed, checked again, released
I repair what broke, the run passes, and only then does the change go live.
$ lint: checking the code style…
An illustration with made-up file names and numbers, modelled on a real test run. Tests do not catch every mistake, but they do catch this kind.
How working together goes. Direct and easy to follow.
One contact
You talk to me, and I am the one who does the work.
Hours you can check
I track my time. The monthly invoice shows what the hours were spent on.
Careful work
I test what I build before I hand it over, and I say so when something is not finished or I am not sure.
What I build is yours
Code and design belong to you. You can hand them to another developer.
Booked by the month. Not by the day.
I work on your project on fixed days of the week, agreed for one month at a time. There is no package to buy: you pay the hours I actually worked.
- Fixed days of the week, agreed for one month at a time
- One invoice per month, with the tracked hours
- Either side can end it with two weeks notice to the end of a month
- I do not book single days
Per hour
100 EUR
net
Example: 2 days a week
about 6,400 EUR
64 hours in four weeks, net
Remote, without fixed office hours
I work from wherever I am and plan my own time. For meetings with your team I am there by arrangement. I am not reachable all day long; in return I work on your project undisturbed the rest of the time.
Good to know before you book.
- How long are we committed?
- Project work is billed by effort. Either side can end it with two weeks notice to the end of a month.
- Can you work with our existing team and code?
- Yes. I worked in agencies and product teams for years, so joining an existing project is familiar to me.
- Who owns the code?
- You do. Code and design belong to you, and you can hand them to another developer.
- What do you not do?
- Mobile apps for the app stores, Windows software and running your servers. If your project needs those, I say so in the first call.
LET'STALK.
Pick what you need and the email writes itself. Or write to me directly:
I need
- to
- hello [at] mintel [dot] me
- subject
- A developer for our product