The application nobody dares touch
It is still critical and still works, but whoever wrote it is gone. Nobody will change a line.
Custom software for businesses that have outgrown off-the-shelf products
We write the software, deploy it in your environment and document how it works. We fix development defects for an agreed period.
What you get, by name
Things you can take with you.
- The software deployed in your environment, not in the supplier’s.
- The source code in a Git repository, where the project provides for it.
- Technical documentation to install, configure and maintain it.
- Training for the people who are going to use it.
- A container deployment that is reproducible and documented.
When a business needs software of its own
A developer is almost always called about something that exists and stopped being enough.
Two systems that do not talk
Somebody opens one, copies a few fields and pastes them into the other. Every day, unmeasured.
What outgrew itself
It works, but new users are needed, or an integration, or something unplanned. It rarely has to be rebuilt.
All three start the same way: understanding what the system does before touching it.
Is this what you need?
If your case is not quite this one:
- If the process already exists and only needs to run on clear rules, that is an automation: Automations
- If something ambiguous has to be interpreted, classified or written, that is artificial intelligence: AI Consulting
How a development project runs
Four steps; the first makes the quote mean something.
Scope and definition
What the software must and must not do, and who uses it. This stage is paid and comes before the price.
Building
It gets written and documented at the same time. Python, Go or SQL Server, with reproducible container deployments.
Deployment and training
It is installed where it will live, and whoever uses it daily is shown how.
Fixes and follow-up
Defects in the development are fixed at no extra charge for an agreed period. New features are a separate job.
Who this is for, and who it is not for
A good fit
- Businesses with a critical internal application nobody maintains any more.
- Anyone with two systems that work separately and nobody to join them.
- Anyone who needs to extend something in use without rebuilding it.
Not a fit
- Anyone wanting a mobile app from scratch with no scope, budget or need.
- Anyone after a product to sell to others, with no definition and feasibility stage.
- Modernising complex legacy systems that demand specialist knowledge that is not here.
Frequently asked questions
Is the code mine?
Yes where the project provides for it, handed over in a Git repository. Agree it beforehand.
Do you build mobile apps?
Web applications that work well on a phone, yes. Native app-store applications, no: none have been delivered.
What is it written in?
Python, Go and SQL Server mostly, with containers for deployment and Git for version control.
Can we start with something small?
The recommended way. Optimising a database and its queries gave a performance improvement of around 25% without touching the rest.
What if my current application was built by someone else?
That is the usual case. The first step is understanding what it does; what makes sense follows from there.
Tell us about your situation
Tell us what your system does today. The first call costs nothing.
Tell us what’s broken+34 600 237 257info@isitechconsulting.com