Many of the companies we work for have no developer, no IT department worth the name, and no wish to hire one. That is precisely why they call us. You do not need to speak our language. We need to learn yours.
One person who knows the business
We ask for a single point of contact on your side. Not a technical profile: someone who knows how the work is really done, including the exceptions nobody wrote down, and who can decide or knows who decides.
In return, that person has a single point of contact too: the engineer who designs and builds, on a direct line, without an account manager in between.
About half a day a week
That is the realistic commitment, and we prefer to say it before the project than to discover it during. The time goes into three things:
- Answering questions. “What happens when an order is cancelled after delivery?” Only you know.
- Trying what was built. The test environment is always up to date. Ten minutes of real use tells us more than a long meeting.
- The demo, every two weeks. You see the working version and we agree on what comes next.
A workshop to start
Before the first sprint, a scoping workshop brings together the people who will use the tool. We listen, we look at the files and the screens they use today, and we leave with a roadmap everyone has seen.
Everything technical is on us
Architecture, security, hosting, updates, the choice of tools: you do not have to have an opinion on any of it. We explain our choices in plain language, and we make them for you.
What it means for you
A project like this does take some of your time, and anyone who says otherwise will build the wrong product. But it takes the time of someone who knows the business, not of a technician you do not have.