Email meIT

Doing one simple thing means opening three programs and a spreadsheet.

Custom business software and web app consulting

The right business software mirrors the way you work, and three years from now someone will still be able to change it. To get there I start from the problem: where time is lost, who does what, which data is needed and by whom.

Then we pick the tool. Sometimes it’s an existing product to configure, sometimes software built for the purpose and connected to what you already use.

How I approach it

Before talking about software I look at how you and your team work today: who does what, in which order, where someone waits for someone else and where data gets retyped from one program into another. That tells me what you need to solve that specific problem.

The mistake I see most often is a very long workflow, with many steps in a row. Every extra step is a place where something can go wrong, and the chances of error add up. So before automating a workflow, I try to shorten it.

Before writing a single line of code I break the problem into smaller parts and show it to you, with workflow diagrams and written descriptions of what happens at each step, who does it and with which data. We correct it together until it matches how you work. The code comes last, when we both know what it has to do.

When it helps

  • The software you use forces you into workarounds, and every change takes weeks.
  • Your business software grew piece by piece and only one person knows how it works.
  • You run several platforms, each with its own users and passwords.
  • You need to choose between an off-the-shelf product and a custom build, and want advice from someone who sells neither.

What's included

  • Process analysis, to find where time is lost and where errors start.
  • A comparison of off-the-shelf software, customising an existing product and a custom build, with the cost of each route.
  • Design of data, roles and workflows.
  • Integrations with what you already use: invoicing, payments, third-party APIs, single sign-on (SSO) across platforms.
  • Development of the web application and, when needed, the mobile app.
  • Documentation and handover, so the software doesn't depend on me.

An example

What you get

  • Analysis document with the options considered.
  • The software, delivered in your repository.
  • Technical documentation and user instructions.

FAQ

Should I go custom or off the shelf?

It depends on how specific your processes are. If an existing product covers the work well, I'll tell you and help you choose it. Custom pays off when adapting to the product costs more than building.

Which technologies do you use?

I choose them based on the project and on who will maintain the software after me.

Further reading

Let’s talk

info@giusepperusso-dev.it

Want to know if it fits your case? Send me a couple of lines about the problem: I reply within 24 business hours.

book a callLinkedInGitHub

Other services