Developer workflows
How people use AI for testing, review, documentation, debugging and repetitive work.
Growth
Turn AI use into better work.
For engineering teams with AI already in the workflow. Find the improvements that matter—in tools, working practices and automation—and decide how to measure their value.
- The engagement
- AI Development Optimisation Review
- Who it is for
- Engineering teams with company-managed tools, basic guidance and established development practices.
- Duration
- Fixed scope and schedule agreed before work starts
- Your involvement
- Questionnaires, focused interviews and screen-shares
- Access
- No source-code access by default
Something you can act on
What you receive.
You know which changes are worth making, what to try first and how to tell whether they improve software delivery.
- An AI development capability assessment: existing strengths and unused capability.
- A workflow opportunity map for engineering activities where AI could add value.
- Tool and configuration recommendations, including repository context and instructions where relevant.
- Engineering practice recommendations and a deliberately short list of priorities.
- A measurement framework for delivery, quality and developer experience.
- A 30/60/90-day optimisation roadmap with owners, effort and expected outcomes.
- A management readout and follow-up, with the scope agreed in advance.
A familiar situation?
Made for this moment.
- Your team has good foundations but mainly uses AI as autocomplete.
- You want to improve testing, review, documentation or maintenance workflows.
- You are considering agentic development and need a sensible starting point.
- You want evidence of value beyond how many licences you pay for.
You do not need to buy the three services in sequence. Start with the question that matters to your business now.
A focused review
What we look at.
Tools & configuration
Repository instructions, context, agent environments, connectors and overlapping tools.
Value & learning
Delivery and quality measures, developer experience and sharing successful practices across the team.
An optimisation review, not implementation by default, a maturity score or a paid tool recommendation. If visibility and control are the main gap, Foresight is the more suitable engagement.
Clear scope. Low disruption.
How it works.
Understand the work
Focused interviews and screen-shares reveal how people actually work and where capability is unused.
Find worthwhile changes
We weigh practical improvements to tools, configuration, automation and engineering practices.
Make progress measurable
You receive a focused roadmap and measures that help you evaluate the changes.
No open-ended engagement
A clear commitment.
One fixed fee for a defined scope. You know what you are buying and what you will receive.
Growth
A fixed fee, agreed upfront
We confirm the fee (excluding VAT) after the introductory conversation and set it out in writing before any work begins. This is a defined engagement, not an open retainer.
Payment and cancellation conditions are set out in the terms of business.
Good questions
Before we talk.
How is Growth different from Foresight?
Foresight gives teams visibility and control over existing AI use. Growth assumes those foundations are in place and focuses on workflows, capability and measurable value.
Will you recommend switching tools?
Only if it serves your goals. Intensive Investments does not sell licences or take vendor commissions.
Why is there no published numeric price?
The first engagements need a clearly agreed scope. You receive a fixed fee in writing after the introductory conversation, before any work starts.
Do you implement the changes?
Implementation is not included by default. The core deliverable is a practical roadmap your team can act on; any additional work is discussed separately.
Do you need repository access?
Not by default. We use questionnaires, conversations and screen-shares to understand working practices.
Is delivery in English?
Yes. Your internal documents can be in Swedish. Work can be delivered remotely or in Skåne and Copenhagen.
Delivered by Alan Ljungström-Caunt. Twenty-five years in software, CTO experience, and independent advice. You work directly with the person carrying out the review.
Meet AlanA good next step starts with a conversation.
25 minutes to find out what would help.