Skip to content
Français

Tell me what is slowing you down

Five fields, two minutes. I reply within one business day, by email or phone.

I automate the work that eats your team's time

Financial reporting, outbound, internal tools. I design, build and ship to production, then I hand you the keys.

Tell me what is slowing you down

Five fields, two minutes. I reply within one business day, by email or phone.

What I do

Who I work with

Four ways to work together

Every project starts with the same question: what work, done by whom, costs how much time today.

  • ERP & business software

    I build proprietary tools that generate revenue inside your business.

    • Full build: interface, database, access control
    • Your existing files carried over, with no re-keying
    • Connected to the tools already in place rather than replacing them wholesale

  • Automation & AI agents

    High-volume tasks go automatic, and agents handle what used to need reading: triage, extraction, drafting within set bounds.

    • Automated reporting
    • Automated GTM and outbound
    • Logs and alerts: failures show up instead of slipping through

  • Internal DevOps

    Your internal tools keep running without anyone watching them. Deployment, backups, alerts: what keeps a project alive six months after delivery.

    • Automated deployment, rollback in a single command
    • Backups, logs and alerts in place from the first release
    • Runbook written for your team, not for me

  • Training

    Your teams learn to build and maintain what I have shipped. On your own cases, with your own files, not a demo example.

    • Sessions built on your real cases, prepared in advance
    • Day-to-day use of AI tools, limits included
    • Materials and recordings that stay with you

What eats up most of your time at work today?

Do not try to frame a project. Describe the task you redo every Monday, the one you have been doing by hand for two years because nobody ever found the time to deal with it.

Write down whatever comes to mind, unstructured, unpolished. I read everything, and I will tell you what can be automated. And what cannot.

An answer within one business day, from me.

Your email and message are used only to answer you. Privacy policy

For example

Client case

Latest project

Management reporting: from five weeks to one hour

Asset manager of 7 funds

  • Google Apps Script
  • Claude API
  • QuickChart
  • Docs & Sheets API

Newfund used to send its management reports three to five weeks after the accounting data was available. Today they go out the same day. Same layout, same charts, same identity, except the finance team regenerates them itself, across all seven vehicles. The accounting data comes in, you click, the report comes out. The external design contractor went away with the delay.

Read the full case study

  • 1 hr

    per report, review included

  • 30 sec

    to generate a complete report

  • 0

    external design contractor

  • Healthcare fund, investment stage

    Automated scientific sourcing

    2 hrs / week

    Public scientific data used to be combed through by hand. An application now aggregates it and turns it into usable insight: two hours of research handed back to the investment team every week.

  • Consumer platform, peak season

    Personalised document production

    1.5 weeks

    Personalised documents used to be composed one at a time. They now come out in batches, unattended: a week and a half of work handed back to the teams at the height of peak season.

FAQ

  • What do you actually do?

    I start from one specific process and put a number on the time it costs today. Then I build the thing that absorbs it: a document that regenerates itself, a flow that fills your CRM, an internal tool, an agent that triages. I stay across the whole chain: understanding the work, designing, building, shipping, training.

  • How long does it take?

    One to two weeks to scope and price, three to six weeks to the first system in production. I split the work into phases, each with a deliverable agreed up front: you can stop at the end of any one of them.

  • What happens once the engagement ends?

    Everything sits with you: code repository, documentation, access, schemas. Your teams have been trained and the system runs without me, which is how I judge the work. I stay available for changes, never because of a technical lock-in.

  • Is your data protected and your project GDPR-compliant?

    You decide where your data is processed: a commercial API with a no-training commitment, a dedicated cloud instance, or self-hosted on your own infrastructure. That is an explicit scoping decision, not a technical detail discovered at the end. On GDPR, the project starts from minimisation: only the necessary fields move, access is named and logged, and the processing I put in place is documented so it can enter your records.

  • Do we have to replace our current tools to automate?

    No. I connect to what is already in place: your CRM, your mail, your accounting, your files. Replacing a tool is your decision, taken on its own merits, not because an automation demands it. When a tool genuinely blocks the work, I say so, with the cost of keeping it stated alongside.

  • Can we automate without technical skills in-house?

    Yes, and that is the most common case. What matters is that someone knows the process being automated, not that they can read code. I deliver documentation written for your team and training on your own cases. If nobody can take over in-house, I say so at scoping rather than after go-live.

  • Who owns the data?

    You do, without reservation, and the code built for you as well. I only access what the engagement requires, access is closed at the end, and nothing I handle for you is used anywhere else.

Let's talk.

Thirty minutes is enough to know whether there is a worthwhile use case. If there isn't, I will say so.

Book a slot

Tell me what is slowing you down

Five fields, two minutes. I reply within one business day, by email or phone.

julien@hasscorp.frLinkedIn ↗