Solved problems,in short.
The situation, what I proposed, what I fixed and what the client gained afterwards.
- Online store
The store's search didn't understand what the customer wanted
Customers find the product even if they don't know what it's called, and the store sees in the statistics what people actually look for.
- Stories
HTML learned in the city's internet cafés
I still learn the same way today: I try, see what comes out, then fix it.
- Online store
Product clicks and add-to-cart: what a chat really tells you
The store sees whether the assistant leads people to a product and to the cart, not just whether it is used.
- SEO
The page title decides whether anyone opens you from Google
The pages are easier to find and clearer in the results, which helps both with ranking and with clicks.
- Stories
Software built to run well on little memory
Today, when resources seem unlimited, I apply the same rule: fast, lightweight applications that run well even on a weak phone.
- Online store
Prices and stock in the chat, the same as in the store
The customer gets recommendations they can buy, at the real price in the store.
- Online store
An assistant in your store, installed in three steps
The store has a working assistant without stopping sales and without an integration project.
- Full platform
A platform that grows from one car park to a whole network
The company can expand its network without rebuilding the system every time.
- Full platform
Validating the vehicle at the entrance, from an image
Access is faster, and a manual step disappears from the process.
- Full platform
Adding a new car park, without needing a developer
The team adds a new car park on their own, and much faster.
- Stories
On a 486 I discovered Flash, before CSS had animations
Today, when animations are done in CSS, I still first ask what the effect adds for the person visiting.
- Full platform
A faulty device at the entrance, fixed without a trip
Many problems are solved without anyone travelling to another country.
- Full platform
Entry statistics: what a car park owner wants to know
The customer sees for themselves how many entries there are and how they change, without asking for a report.
- Full platform
Many car parks across Europe, one screen
The team sees the whole network at a glance, without jumping between systems.
- Full platform
Each customer sees only their own car parks
Customers get a clear picture of what belongs to them, and the data stays separate between them.
- Communication
Someone who doesn't finish the form isn't lost, just interrupted
More customers finish their form, and the team receives complete data without chasing anyone.
- Integrations
Form data straight into Salesforce, with no re-typing
The team no longer re-types, and the data in the system is the same as what the customer filled in.
- Stories
On a 286 I learned Pascal
I still prefer clear code with rules to code written quickly and hard to read later.
- Integrations
The collected data, in a PDF a person can understand
The customer has a clear record of what they submitted, and the team reads the data quickly.
- Integrations
The form can be filled in on a phone, not just on a computer
The customer can fill in the form from anywhere, without having to get to a computer.
- Stories
My first computer was an HC 91
I still start today from something small that works, and grow it afterwards.
- Integrations
A long form shouldn't look long
The form is easier to get through and more customers reach the end.