I build you an application for work that someone at your company still does by hand. It runs on your server, and I keep it running with a monthly subscription.
After our first call, you get a fixed price for the build and a monthly fee for maintenance.
At SIMPLY, the old contact form deleted every enquiry after 14 days. So nobody could look back at the people who had sent a message through the website.
Today the sales team sees every enquiry in one place. They also see the visits, where the visitors come from and which pages they read. Nobody has to type anything in for this. The blog has its own admin area, where the team puts posts with images online by themselves. I built both around the way SIMPLY already worked.
It usually starts with a task that someone at your company does by hand every week. Maybe your inquiries land in several inboxes, and nobody sees what happens to them. Maybe someone types numbers from an old program into another one because the two cannot connect. Or your people send photos and dates to each other on WhatsApp.
For exactly this task, I build you an application that runs in the browser and works the way your team already works today. Your team does not have to learn anything new, except where to click.
See it in the example
Click through a concept for a machine builder’s admin area, with machines, documents with versions and requests with deadlines.
The practice had a WordPress site that nobody there looked after. Today the practice enters its opening hours and notices like “Practice closed” in a small admin area, and each notice turns itself on and off for the planned dates. The statistics count visits and clicks on “Book an appointment” without cookies. Messages from the contact form go to the practice by email and are not stored.
His website ran on WordPress, and I built him his own editor for his essays instead. When a text is saved there, the new website rebuilds itself in about a minute. Until it moves to his own address, it runs as a preview.
I tried a ready-made tool for feedback, but it only saved the sketches in the browser. So I built my own. My clients now comment and draw right on the preview of their new site, and every note is saved on my server, at the spot it refers to.
The software runs on your server or with your hosting company, and the code belongs to you. I get access so I can look after it. Your hosting company makes the backups with its own backup service, so your data does not depend on me.
If you end the subscription, you take everything with you, and someone else can keep working on it.
After the build, I keep the software up to date, fix bugs and add to it when something changes at your company. I plan ten hours a month for this. You write to me what you need, and you get an answer on the next working day.
“… a great new site that I’m proud of, and you have a happy client. And with SIMPLY, your next project.”
“A huge thank you goes to Nils Enders‑Brenner, who turned our visions into reality. Great how he put his creative ideas into practice!”
It is, if a task comes back every week and someone loses time on it every time. It is also right if you already tried software off the shelf and in the end worked around it again. If you only need a new website, the home page is the better place.
After the call I offer you the build at a fixed price, because it depends on what the software has to do. After that you pay a fixed amount each month, and it includes ten hours for maintenance and further work. Before we talk, count how many hours a month this work takes at your company today.
The code and the data are with you, and your host makes the backups. Someone else can keep working on it.
No. The software runs at your host, and I take care of updates and bugs in the monthly subscription.
I check that before the fixed price. If your program has an interface or an export, I can connect to it.
If there is one that fits you, I will tell you in the call.
You probably know the spot at your company where you think every week that this should just happen by itself. Write to me about exactly that spot. A few sentences are enough, the way you would explain it to a colleague.
I read your message myself and reply on the next working day, usually with one or two questions and three dates for a call. On Zoom we spend 15 to 20 minutes on how the work runs today, who does it and where it gets stuck. After that I send you in writing what I would build, the fixed price for it and the monthly fee for maintenance. You decide in your own time, and the call costs you nothing.
When we work together, you have one person who built the software and knows it. You write to me what should change, and you have an answer on the next working day. The code and your data stay with you, even if you stop one day.
And then comes the Monday morning when this work is already done before you get to the office.