we come to you, and your team keeps it.
a day on site with the people who do the work. we teach them to run their own jobs through ai, then build the connections that wire it into the systems they already use.
the test is whether they can do it again on monday without us.
the day.
we sit beside your team and work on their real jobs, the ones already on the list that week. nothing is a worked example. by the end of the day the work is done and the people who did it know how they did it.
then we build the connections. the tools your team uses get wired into your own systems, so the work carries on after we leave instead of living in a browser tab somebody eventually closes.
they keep it
what came out of one.
opms builds systems for the offshore energy sector. their engineers had tried ai tools before and got demonstrations rather than finished work.
we spent one day with them, working through a real piece of their backlog. by the end: a full feature shipped to production, about 3,900 lines across 35 files, five endpoints, eighteen tests, and seven bugs found and fixed on the way.
they kept shipping that way after we left, which is the only number that matters.
read it
who it suits.
the day works when the team already has real work in front of them and the person who owns that work is in the room. an engineering team with a backlog, a practice buried in write-ups, a builder chasing quotes. if your people spend their week on something repetitive and nobody has had time to fix it, that is the day.
we have run it as a half day and as two days. the shape follows the work, so tell us the job and we will tell you how long it takes.
