Less than one hire, and your team ends up capable.
Teach a team to automate its own busywork and the improvement does not leave when you do. It spreads. A monthly engagement where your own people build, while I direct the roadmap, teach, and review everything they make. All remote.
Manual work everyone agrees should be automated.
What our clients have in common is obvious work worth removing, and never the time to remove it.
Drift is the third option. Your own people build, I direct and teach, and the capability stays in the building.
See howMonth one is the survey
Drift starts with the survey. The first month goes to understanding your work and producing the roadmap the rest of the engagement builds on. If it does not produce a clear roadmap, you do not pay for that month.
The survey makes the plan
The first month maps how the work actually gets done and ends in a prioritised plan: a clear roadmap of what is worth automating, with measured baseline numbers. If you do not have that by the end of the month, the month is free.
Your team builds the plan
With the roadmap in place, your team takes one item a month. They build between sessions, I teach and review, and you get a report with measured before and after numbers.
Drift: your team builds,
I direct and teach
Most automation is done to a company. Someone builds a system, hands it over, and leaves the team unable to change it. We work the other way around. Your own people build the automation, I teach and steer, and when I leave they can keep going without me.
The point is not only the hours saved. It is a team that is less overworked, less frustrated with its tools, and more capable than it was. Everything is delivered remotely, in your own systems, which is where the work has to live anyway.
The building months have the same shape
Two scheduled sessions a month where I teach, clear blockers and prepare the next step with your team. The building itself is done by your technical staff between sessions. Everything else runs in writing, answered within two working days.
Week 1 · Pick and measure
We agree the next roadmap item and measure what it costs you today, in hours and kroner.
Week 2 · Working session
90 minutes over screen share. I teach, unblock what is stopping you, and prepare the next step. The building itself happens between sessions.
Week 3 · Build and review
Your technical staff build between sessions. I review what they made and send written feedback against a standard.
Week 4 · Ship and report
The solution goes live. You get a written report with before and after numbers, and next month's item is set.
All three end the same way: less by hand, and you own everything built
The difference is who does the work, and what your team can do when we are finished.
For a team that already has the skill and just needs the method.
- The full methodology library
- Templates and review checklists
- The survey method, documented
- No working sessions or review
For a team that has the people but lacks the direction and experience.
- Two remote sessions a month where I teach and unblock
- A roadmap scoped to your team's time
- Written review of everything built
- A monthly report with measured numbers
- The methodology library is included
For a business that wants the result without involving its own people.
- I do the work instead of teaching it
- Priority on the whole roadmap
- A fresh survey every quarter
- One slot, and only after a Drift engagement
Partner gets you there faster, but when it ends your team knows exactly what it did on day one. Drift costs a quarter as much and leaves you with people who can keep going without me.
What this looks like in practice
A few common things a team builds during Drift. Open any of them for a full walkthrough: the use case, the architecture, and what changed.
Automated reporting & dashboard
A half-day each week spent pulling numbers from different systems into a spreadsheet.
Internal knowledge assistant
Staff repeatedly asking the same questions or digging through documents for answers.
Pre-arrival & onboarding sequences
The same welcome info sent by hand every time, slightly different and sometimes forgotten.
The Automation Context Engine
Worried about AI hallucinating or going off-script? This is how we make AI answer only from your own knowledge: cited, consistent, and auditable. Built on our own infrastructure first.
For businesses that have the people but lack the direction
Drift works where you have technical staff who can implement. The deciding requirement is not budget but capacity: at least one technical person who can build between sessions. If you do not have technical staff, it is probably not the right fit, and I will say so straight away.
The industry matters less than the work. We fit operational, project-driven businesses with repetitive manual work that people can describe in detail.
- You have between 25 and 150 employees
- You have at least one technical person who can implement
- That person has the capacity to build between sessions
- The work is operational and project-driven, with repetitive manual work people can describe in detail
- You want to own the solution, not rent it from a consultant
- You want the capability to stay in the building afterwards
Audun Moseng
Rendata is led by Audun Moseng, an IT architect with 10+ years in enterprise cloud, security, and automation. He has led greenfield architecture for large enterprises, extensive migration projects, and works as a technical advisor and team lead in enterprise managed services.
Rendata runs on the same craft: our own infrastructure is a production-grade, virtualised and container-based platform, with automation, trusted AI, and infrastructure as code. I do not resell anything I have only read about.
Questions we get a lot
Most of what you might wonder before a call.
What does Drift cost?
60,000 NOK a month on a six-month engagement, invoiced monthly. All prices are ex. VAT. Self-serve is 25,000 NOK one-off, and Partner is 260,000 NOK a month.
Do we need technical staff?
Yes. Drift teaches your team to build for themselves, but someone has to do the implementation, and that takes technical skill. In practice at least one technical person with the capacity to build between sessions. If you do not have that, Drift is probably not the right fit, and I will say so straight away.
Is everything remote?
Yes. The working sessions run over screen share, and your team builds in your own systems. It is a deliberate choice, not a compromise, and it means where you are based does not affect the price.
What if it does not fit?
If you do not have a written roadmap with measured baseline numbers after month one, month one is free and you can walk.
Do we own what gets built?
Yes, fully. Lock-in is not a feature, it is the whole point. If your team cannot change it without me, I have failed.
What is the difference between Self-serve, Drift and Partner?
In Self-serve you build yourself with our method. In Drift your team builds while I direct and teach. In Partner I do the work instead of teaching it. Nearly everyone lands on Drift.
Less than a hire, and your team ends up capable.
Book a call about Drift. Tell me how your business runs and where the work feels harder than it should. I will tell you honestly whether Drift fits, or whether it is not the right time.
No slides, no hard sell, no commitment. Just a straight conversation about how your team can do less by hand.