Pamats (Foundation). How the working day changes once Claude is set up for your work.

How it works

1. Talk with your team

   In one day we talk to every person on the team, up to ten, about what repeats in their work every day, week or month. We look for 15 to 20 minute jobs with a digital input: a file or text the person can drop into a chat, steps they could dictate to a new colleague, and a moment where they check the result before it goes on. For each candidate we ask for 3 to 5 real file pairs, before and after. Without them the setup cannot be tested.

   What you get

   • A list of the recurring jobs: the job, how often, how long, where the input comes from, where the output goes, who does it.
   • Notes on your systems and file formats.

   Your side

   • A team of up to 10 for one day, an individual conversation with each.
   • 3 to 5 real file pairs for each candidate job.

2. Process map

   The day's notes become one document: the jobs we found and the payoff of each, as a number, not a feeling. Payoff is frequency times duration times the number of people. Together we pick the three with the biggest payoff that can run as a Claude project without extra connections. Each gets a named owner on your side, the person who said they would like to run it. Without an owner a process stays on the map but does not make the three.

   What you get

   • A process map, one document, which stays with you.
   • Three chosen processes with owners and the business owner's sign-off.
   • The candidates that did not make the three, kept for the day-30 review.

   Your side

   • The business owner's sign-off.
   • Three people who want to run a process themselves.

3. Setup

   We set up each process in your Claude workspace as a project with written instructions: what comes in, what goes out, which terms, which checks, where to stop and ask. We test the instructions on your real files at least three times and fix them after each run before we show the team. Each process gets a one-page how-to card for people who do not use AI every day: where to drop the file, what comes back and what to check. We tidy the Claude workspace on every seat so the projects are visible and the clutter is gone.

   What you get

   • Three projects in your Claude account with written instructions, tested on your files.
   • Three how-to cards, one page each.
   • A tidy Claude workspace on each of up to 10 seats.

   Your side

   • The process owner joins the first test, about an hour per process.
   • Admin access for us during setup. We remove it at handover.

4. Handover

   Handover is an adoption test, not a presentation. Each owner opens the project, drops in today's file, checks the result and passes it on. We are present and quiet, we note where the person hesitates, and we fix the instructions on the spot, not a week later. If something had to be explained out loud, the how-to card is incomplete, and we fix that too. At the end we agree with the business owner where the team writes down ideas until day 30, and we put the review date in both calendars.

   What you get

   • Three processes run by your own hands from start to finish.
   • A handover note: what was handed over, what was fixed, where the idea list lives.
   • Our access removed the same day, everything stays in your account.

   Your side

   • The owners with real files from today.
   • The business owner at the start and the end.

5. Review after 30 days

   The only included contact after handover, and the most important one. How many times each process ran, who ran it, what stalled and why. What you still do by hand. What the rest of the team asks when they see a project working. We sort the idea list: what can be added as extra work, what needs Partnerība, what is not needed. It ends with a dated next step, or a clear statement that the work ends here.

   What you get

   • A status for each of the three processes: used regularly, rarely, not at all, with the reason.
   • The idea list, sorted by what happens to each idea next.
   • A dated next step or a clear ending.

   Your side

   • The business owner and the process owners, one conversation.

If you need more

• An additional process with instructions and an owner
• A connection to your system: Drive, email, CRM, browser
• Additional training for another team or new joiners
• A connection with no ready-made solution

What to add is usually settled in the review call after 30 days.

Who does it

Ents

RRN's strategist and head of communications, who will understand what you actually need and work with the team to find the right answer to it.

Ents has founded and run companies in Latvia and in Asia, and has worked in senior positions in the public sector. The best results, though, come from pairing an older management style with the newest technology.

AI drafts his documents, market research and PR copy in seconds, leaving the time for what only a person can do: the decisions and the strategy. It makes the road from a client's problem to a working solution a good deal shorter.

In his own time Ents uses AI as a sparring partner in philosophy. Drawing on years of reading in theology and philosophy, he has trained it to argue with him about the large questions, and to test whether his own thinking survives honest criticism.

Matīss

Responsible for rolling projects out, for the improvements that follow, and for client support.

Matīss has used AI every day for the last 6 years, and has spent 3 of them putting it to work on the job.

When he started using Claude Code, he saw straight away that AI could take over all the routine he had long been tired of and move forward projects that a few years ago looked impossible without a seven-figure investment.

At home he has put AI to work as a chef: he types in the ingredients and gets today's meals back.

Rūdolfs

Founder of RRN, who will draw up your AI growth path and make sure you stay on it.

Rūdolfs has been an AI enthusiast since the very beginning, gaining his experience at Accenture and Giraffe360 before RRN.

AI lets him work on 10+ client problems at once with clear communication and fast answers.

In his own time Rūdolfs likes building everyday AI systems for his wife, to make her life a little simpler and more productive too.

Frequently asked questions