Working together

How does your business application get built?

We start with a description of what you need. Next comes a plan and estimate, followed by development if you decide to proceed. You commission planning and development separately.

A short description is enough to get started.

Your enquiry and the next step

Describe one situation you want to change: preparing a quote, handing over a job or entering the same information twice. I will reply by email, let you know whether I can help and ask for any details I need. If a conversation would make things clearer, I will suggest a free call of about 20 minutes.

At this stage, we establish whether I can build the solution you need and whether it fits your budget. Detailed planning is a separately agreed, paid stage. Sending an enquiry does not commit you to it.

The solution plan

We choose one task and look at real examples of how it is done. The basic scope includes up to two conversations with the people who do the work and a review of the agreed materials.

You receive a document covering:

  • the current way of working, problems and exceptions;
  • a comparison of improving the current tool, buying existing software and building an application;
  • sketches of the main screens and the scope of the first version;
  • how the finished application will be checked, along with dependencies and risks;
  • the development cost and schedule.

Price from €850 excluding VAT. A basic plan usually takes 1–2 weeks after the materials are provided; we agree the deadline before starting. You can commission this stage alone and use the document with another developer.

The first application version

Before development, we agree the features, user group, data source, price and schedule. An example scope is a job register with documents, deadlines and employee roles, plus an export in an agreed format. Full ERP synchronisation, automatic drawing interpretation and production planning require separate agreement.

I show progress through short demonstrations or reports. Selected employees test working versions using agreed examples. If a new idea comes up, I explain its impact on cost and timing before implementing it.

First version from €4,300 excluding VAT. An indicative budget is €4,300–8,300 excluding VAT, with a timeline of 6–10 weeks from the agreed start, once the required data and access are available. The proposal sets out the exact scope, payment terms and dates.

Planning and implementation are charged separately. The plan’s price is not automatically deducted from development. The combined starting budget for both stages is €5,150 excluding VAT, before maintenance and external services.

Launch and handover

We check the agreed scenarios, access for each type of user, backups and restoring data. We agree how to migrate existing data and what to do if something goes wrong during launch.

I hand over the documentation, instructions and access specified in the agreement. Before development, we establish the terms for code, licences, accounts and future development, so it is clear how work can continue after our engagement ends.

Maintenance and further development

Before launch, we agree the costs of the server or cloud service and external services, support availability and responsibility for backups and updates. These costs are separate from development.

After launch, we collect employee feedback. Correcting a defect against the agreed scope, routine maintenance and adding a new feature are different types of work. The agreement defines how each is handled.

What I need from your side

One person to coordinate decisions, access to future users and decisions made by the agreed dates. You do not need technical knowledge. I need your understanding of how the company works and time for employees to check successive versions.

Before enquiring, the guides on describing application requirements and what makes up the cost may help. Before launch, you can also use the rollout and data migration plan.

PRACTICAL DETAILS

Questions before we work together.

Do we need a technical brief or a meeting first?

No. A short description of one task is enough: how you prepare a quote, pass on an order or enter the same data twice. I will reply by email and ask any questions. If a conversation would help, I will suggest a free call of about 20 minutes.

Do we need to replace our current software?

Often you can keep it. An additional application can handle the missing task and use data from your existing software. I first check data access, licences and integration costs. Configuration changes or an existing module may be enough.

What costs should we expect after launch?

Server or cloud costs, third-party services and agreed maintenance are quoted separately. Before launch, we agree on costs and responsibility for backups, updates and support. New features require their own scope and estimate.

Can we order a plan without building an app?

Yes. The solution plan is a standalone service from €850 excluding VAT. It includes recommendations, screen sketches, the first version’s scope, a development estimate and acceptance criteria. You can use it with another developer. Its price is not automatically deducted from development.

Is a custom application always the best option?

No. I also check whether configuration changes or ready-made software would be enough. I recommend a custom application when it makes sense for the company’s work and budget.

Who owns the code and accounts?

Before development, the agreement sets out the handover of code, documentation and access, along with third-party licences. We agree which accounts your company owns and how another developer could continue the work.

What if the scope changes during development?

I explain the impact on price and timing before making the change. You decide whether to revise the current scope or keep the idea for a later stage.

Do you build websites too?

The main offer is applications for business tasks, employee and customer portals, and software integrations. We can include a website when it is part of that solution.

Can you start with a complete system for the whole company?

That needs a broader plan and a review of the skills and time required. I recommend starting with one important task that your employees can test in practice.

START WITH A MESSAGE

Describe one task that takes too much time.

Tell me how it works today and which software you use. I will reply with where it makes sense to start.

Describe what you need

A few sentences are enough. No technical brief needed.