How I work
One person from the first conversation to deployment. We start with the problem, and I choose the technology only after that.
Working together doesn't end at deployment: conversation, plan, build and test, deployment, then fixes after launch and growth. We start with one process, the one that takes the most time, and add more once the effect shows.
You are here: How I work.
How working together looks
The first half of the loop leads to launch, the second is what happens afterwards. We'll fit the details to the project.
- 01ConversationYou know whether it's worth it
You tell me how you work today and what's in the way. After the conversation you know whether it can be solved and where to start. If it isn't worth it, you'll hear that too.
- 02PlanYou know what will be built and for how much
Before I start building, you get the solution, scope, priorities and price in writing. We start with the version that solves the most important problem.
- 03Build and testIt works before people see it
I build and check the solution on situations from your everyday work. I polish the details before the team sees it.
- 04DeploymentThe team starts using it
I prepare everything for everyday use and show how to use it. This is usually where a project ends. Here the loop goes on.
- 05The first weeksFixes after meeting reality
Everyday work shows things that tests don't. I fix them before anyone starts working around them in their own way.
- 06GrowthIt grows with the company
When a new need appears, we don't start from scratch, just from the next conversation. The scope of ongoing care is agreed separately, if you need it.
What you get at the end
- A working solution, tested on test data.
- An explanation of how to use it.
- A description of what it takes to maintain it.
- Access to all the parts that were built.
The cloud or your server?
Whether a tool runs on your server or in the cloud follows from the requirements, not from fashion. Your own server isn't secure by definition: updates, backups, access control and monitoring are always needed.
How payment works
Two models to choose from. The scope and quality are the same; what differs is how you pay and who owns the code.
One-off
You pay once for the project.
- The code written for you passes to you after payment.
- It runs on your own account: with a hosting provider, in the cloud or on the company's server.
- Maintenance and further changes, if needed, under a separate agreement.
Subscription
A setup fee to start, then a fixed monthly fee.
- Hosting, updates, backups and small changes are included.
- You use it under a licence, and after an agreed period you can buy it out.
- A lower cost to start, and I take care of the technical side.
Questions and answers
What if I don't know what I need?
You don't need to know whether you need an automation, a website or an app. Write what's causing trouble and I'll reply with what can be done about it.
Do you work alone?
Yes. InfinityInbay is one person: the same one talks to you and writes the code.
How do we agree the scope?
Once the problem is understood, I propose a solution and scope in writing. We start with the version that solves the most important problem.
What do I get when it's finished?
A working solution and an explanation of how to use it and what it takes to maintain it.
What do the contract and payment look like?
I don't run a registered business, so contracts and billing go through Useme (useme.com). We write the scope, price and deadline into the offer, I set up the order in Useme based on it, and you get an invoice from Useme and pay through the platform. Useme concludes the contracts and handles the taxes, so everything is formally on paper.
Can I pay once or as a subscription?
Yes, there are two models. One-off: you pay for the project, and the code written for you passes to you after payment. Subscription: a setup fee to start, then a monthly fee covering hosting, updates, small changes and support. On a subscription you use the solution under a licence, and after an agreed period you can buy it out.
Who owns the code?
In the one-off model, you do: after payment the economic rights to the code written for you, including the right to change it, pass to you, and you get all the code, the access details and a description. Open-source libraries stay under their own licences, and my own tools that I use across projects come to you under a licence included in the price. On a subscription the code stays with me and you hold a licence for the term of the agreement or until buyout.
Are revisions included?
After handover you have 14 days to test: I fix anything you report in that time within the price. Bugs, meaning anything that doesn't work as we agreed, I fix at no extra cost for 30 days after acceptance. Later changes and extensions are quoted separately, depending on their scale.
Where will it run, and who pays for hosting?
In the one-off model, on your own account: with a hosting provider, in your cloud or on the company's server. I help set it up, and fees go straight to the provider, so you don't depend on me. On a subscription, hosting is on my side and included. The domain is always registered to you.
What happens after launch?
On a subscription, maintenance and small changes are included. In the one-off model I can look after them under a separate agreement, or hand over the documentation so someone else can. Your choice.
Do you use AI?
Yes, as a tool: when writing code, text and graphics. I check everything and take responsibility for the whole, as for my own work. Your data and documents don't go into external AI tools without your consent, and if needed I work without cloud AI or run a model on your own server.