We augment our team into yours, using the same repositories, tools, and ceremonies. The aim is a family-style way of working built on trust, shared contexts, and pace.
Come with the work that feels heavy.We are happy to make it feel light.
Boutique IT consultancySenior deliveryFixed accountability
Senior delivery. Fixed accountability.
A boutique IT consultancy for embedded software delivery, modernisation, technical diligence, and strategic advisory.
- MalmöBased in Sweden since 2019, working with founders, investors, and engineering leaders who want a clear owner.
- One leadOne named technical lead stays accountable for the engagement, from the first brief through handover.
- Senior rosterSenior people do the work. Decisions stay written down so the assignment remains understandable after we leave.
Work as one team.
We join your repositories, tools, and ceremonies with one named technical lead accountable for the engagement.
- Same reposWe join your repositories, tools, and ceremonies instead of running a parallel vendor process beside the team.
- Named leadOne technical lead owns the relationship and the technical direction for the length of the assignment.
- Shared workThe aim is a family-style way of working: trust, shared context, and pace, because that is how the work holds up.
Modernise without losing control.
We improve applications, platforms, and data systems in practical phases, adding AI only where it earns its place.
- Phased changeWe improve applications, platforms, and data systems in practical phases rather than betting everything on a rewrite.
- Keep controlThe current system stays operable while the work is in progress, so ownership and delivery never go dark.
- AI when usefulWe add AI only where it earns its place against real acceptance criteria and the people who will operate it.
Make the decision with evidence.
Technical diligence and strategic advice based on architecture, operations, team capability, security, and delivery risk.
- ArchitectureWe examine how the system actually works: structure, interfaces, data, and the constraints that shape the next decision.
- RiskOperations, security, team capability, and delivery risk sit in the same written view, not in separate conversations.
- Written judgementThe report reflects the judgement we would act on ourselves. We do not recommend a path we would not stand behind.
Westructureuncleartechnicalwork,deliveritwithyourteam,andleaveownershipbehind.
Senior people. Clear ownership. Work that holds up.
Small roster. Named owners. Shipped outcomes.
Adamass AB is a boutique IT consultancy in Malmö, Sweden, founded in 2019. The practice takes named ownership of generative AI, machine learning engineering, legacy modernisation, and technical due diligence for investors and founders. Most work is team augmentation with written scope and milestones — engagements have run from a few months to about three years.
Most problems arrive between strategy and engineering, prototype and production, or documentation and operations. We structure the work, deliver it with your team, and keep one person accountable.
We do not add process for its own sake. Decisions, assumptions, and changes are written down so the work remains understandable after we leave.
Engagements close with source, configuration, deployment notes, and operational documentation transferred as agreed in scope.
Organisations we can name in public.
What we take on.
Three ways in: inside your team, through a system that needs replacing, or as written judgement before a decision.
Embedded software delivery
We join an existing engineering team and work in its repositories, tools, and ceremonies. One named lead stays accountable. The work can cover applications, platforms, data, or production AI where it is genuinely useful.
Modernisation and AI integration
We assess ageing applications and data platforms, find the expensive constraints, and replace them in phases. When AI belongs, we design it around acceptance criteria, existing systems, and the people who will operate it.
Diligence and strategic advisory
We examine software assets for acquisitions, investment, or internal decisions. The written report is the judgement we would act on ourselves. We do not recommend a path we would not stand behind.
Structure without the consultancy theatre.
The exact shape changes with the assignment. The principles do not: visible scope, senior ownership, useful documentation, and a clear transfer of responsibility.
Selected work.
Two public engagements. A closed-corpus, on-prem model for European M&A that reads the data room and drafts a first-pass note a partner still signs. And a paediatric diagnosis stack taken off MATLAB onto a Python inference service.
Most recent
A fine-tuned model for European M&A.
Post-trained on a closed corpus of investment files. It reads the data room, drafts the note, and stays inside the mandate. A partner still signs.
M&AEUOn-prem
The corpus
Data roomsSPAsSide lettersBoard packsDisclosure lettersWarranty schedulesCIMsQ&A logs
First pass
75%
faster than a senior reviewer
Fine-tuned weights
22B tuned72B total
What the model does
- Flags material findings in the data roomgrounded
- Cites the clause it appliedcited
- Drafts the first-pass notedrafted
- Ranks findings by materialityranked
- Refuses outside the mandateguardrail
- Leaves the closed corpusnever
- Signs the opinionnever
Next step
Ask about a similar engagement.
Modernisation
A paediatric diagnosis stack, taken off MATLAB.
Scoring left a MATLAB runtime for a Python inference service. Retrieval-augmented chat reads the closed report. A second model emits level specs into a web game engine for intervention.
DiagnosisPaediatricSFT
The corpus
Item banksNorm tablesIRT parametersResponse vectorsClinician reportsError profilesSession tracesLevel specs
Runtime
1
scoring service, off MATLAB
Exercise model
SFT on the item bankSchema-constrained decode
What the model does
- Retrieves the closed report packgrounded
- Answers only from scored itemscited
- Emits a level spec for the enginegenerated
- Keeps items on the constructschema
- Adapts difficulty to the error profileadaptive
- Revises the diagnosisnever
- Signs the clinical opinionnever
Next step
Ask about a similar modernisation.
Now that you've seen the work,see how we actually run it.
Write the problem down first.
We write down objectives, constraints, assumptions, and success criteria before delivery begins.
- ObjectivesObjectives, success criteria, and the shape of the outcome are written down before delivery gets expensive.
- ConstraintsAssumptions, limits, and open questions stay explicit so later changes can be judged against the original brief.
- Named ownerOne lead is named at the start and remains accountable for scope, decisions, and the quality of the write-up.
Deliver in the open.
We work in your systems, keep decisions visible, and adjust against evidence without losing ownership.
- Your systemsWe work in your repositories, tools, and ceremonies so the work lives where your team already operates.
- Visible decisionsProgress, decisions, and changes stay written and traceable. Nothing important lives only in a call.
- EvidenceWe adjust when the evidence changes, without losing ownership or turning the assignment into open-ended theatre.
Leave the work in their hands.
Source, configuration, operating notes, and context move to your team when the assignment closes.
- SourceSource, configuration, and deployment notes move to your team when the assignment closes, as agreed in scope.
- Operating notesContext, decisions, and how to run the work are written so the next person does not have to reconstruct them.
- Your teamOwnership should not depend on us staying. The engagement closes when the work is demonstrably yours.
hello@adamass.se
Send a short brief to Adamass AB in Malmö. We reply with availability, then use an intro call to confirm fit, scope, and timing.