Skip to content
Santiago RicciEntrepreneur · Investor
Software

Before I was a consultant I was a software engineer. I still am.

Internal tools, automation and integrations for companies already operating. Code gets written when code solves a business problem, and not before.

I trained as a software engineer and I have not abandoned it. It gets applied to whatever a company does by hand, does twice, or does in a spreadsheet nobody understands any more.

What I build

Internal tools: what your team does by hand today in spreadsheets, with the human error that carries and the time it consumes.

Integrations: making the systems you already pay for talk to each other, instead of someone copying data from one to the other every Friday.

Automation of operational processes, with the business logic inside the system rather than spread across three people's heads.

And technical audits: reviewing what you have already had built and telling you what holds up, what has to be redone and what you are being overcharged for.

How I work

I start with the process, not the technology. Most software projects that fail in a small or mid-sized company fail because a badly designed process was automated: all that achieves is getting it wrong faster and at greater scale.

No bloated platforms and no dependencies that cannot be sustained. If your team cannot maintain what has been built once it is finished, the project has failed even if it works.

The code and the documentation are yours. No lock-in and no ransom fees.

What I do not do

I am not an agency. I do not build corporate websites to order, or campaigns, or piecework development with subcontracted teams.

I do not build systems for managing third-party funds, investment platforms, gateways for trading crypto-assets, or anything that requires authorisation from a financial supervisor in order to operate.

How it is delivered

How a project is delivered

With partial deliveries from the start. No six months in the dark.

  1. 01 Process
  2. 02 Scope
  3. 03 Deliveries
  4. 04 Handover

Who it is for

  • Going concerns with manual processes that already cost more than a tool would.
  • Companies with several systems that do not talk to each other.
  • Anyone who has inherited an existing development and does not know whether to keep it or scrap it.
  • Groups that need to consolidate information from several companies.

Who it is not for

  • Anyone looking for a corporate website or an online shop.
  • Startups looking for a technical partner who contributes work in exchange for equity.
  • Projects that require authorisation from a financial supervisor in order to operate.
  • Anyone who wants a fixed price before anyone has looked at the process.
Format and fees

Format and fees

Quoted per project after mapping the process, which is short and is billed, because it already produces usable conclusions even if the work goes no further. I do not work by the hour and I do not keep open-ended support retainers.

Propose a project