Fundamentalco Acquires Move38 AI Studio
Fundamentalco acquires Move38 after working with the Amsterdam AI studio on its internal platform, bringing an existing technology partner inside the consultancy. The acquisition, reported on November 20, 2026, gives the buyer a closer connection between strategic advice and software delivery. It does not yet establish that combining those capabilities improves client results.
The distinction matters for companies buying AI transformation services. A consultancy can recommend a new direction, demonstrate a prototype, and still leave the hardest implementation decisions unresolved. Owning the development team changes who can address those decisions. Whether it changes the outcome depends on what reaches everyday use.
There is an established precedent for combining consulting, creative work, and product development. Accenture Song’s acquisition of Work & Co put those capabilities under a larger organization. Fundamentalco’s transaction follows that broad direction, with a narrower focus on AI. Its central tension is straightforward: bringing builders inside creates more delivery responsibility alongside the opportunity to sell broader engagements.
Fundamentalco Acquires Move38 After an Existing Collaboration
The acquisition turns a working relationship into an internal capability, rather than starting an AI practice from scratch.
According to Steve McClellan’s reporting on the Move38 acquisition, the transaction includes the studio known for its proprietary SteelframeAI platform. Founder George Strakhov, previously DDB’s global head of creative technology, joins Fundamentalco in a technology leadership role.
The companies had already developed an internal AI platform that draws on Fundamentalco’s previous work to support consultants and produce project materials. That collaboration provides a concrete starting point. It also explains why ownership, rather than another partnership announcement, is the relevant change.
Fundamentalco’s stated ambition extends beyond its internal strategy team. The company wants to build AI products and prototypes for clients while incorporating AI earlier into transformation projects. It also intends to expand AI use across its own operations.
Those are plans for how the combined organization will work. They should be read separately from evidence about what clients have gained. Neither owning a platform nor acquiring its developers establishes a measurable improvement in project quality, implementation speed, or business performance.
The acquisition nevertheless changes the practical options available during an engagement. When a strategy team identifies a proposed service or workflow, it can involve colleagues responsible for building it. That creates an opportunity to test assumptions before a recommendation becomes a final deliverable.
Consider the difference between describing a new customer experience and putting a working version in front of customers. The description can communicate an ambition. The working version exposes choices about information, interaction, reliability, and maintenance that a presentation can leave unresolved.
This is an analytical implication of the transaction, not a claim about a particular completed client project. The reports establish a closer organizational connection between strategy and development. They do not establish how consistently that connection will produce useful software.
The prior collaboration should also make the integration easier to assess. Fundamentalco already has experience buying the studio’s work. Future reporting can therefore ask what ownership adds beyond the relationship that existed before the acquisition.
A useful answer would identify a change in delivery: broader access to engineering expertise, clearer responsibility, or better support after launch. Without such evidence, the acquisition remains a change in capability and ownership. That is meaningful news, but a different category from demonstrated client impact.
The Pressure Moves From Recommendations to Delivery
Bringing an AI studio inside raises the standard for what Fundamentalco must deliver after a strategy engagement.
The immediate pressure falls on the buyer’s own operating model. Its account teams must connect strategic commitments with engineering capacity. Its technical leaders must decide which proposed applications deserve development. Senior consultants must accept that testing can expose weaknesses in an attractive recommendation.
That last point is essential. A prototype, meaning an early working version used to test an idea, is useful partly because it can contradict the strategy. If development only illustrates decisions already considered final, the organization loses much of the benefit of having builders involved.
For clients, the potential advantage is a shorter path between identifying a business problem and testing a proposed response. The commercial question is whether that shorter path survives the realities of implementation. Access permissions, data quality, existing systems, and employee habits all affect what can actually ship.
An internal engineering team cannot simply remove those constraints. It can bring them into the discussion earlier. That changes the quality of a recommendation when technical findings influence the proposed scope, sequence, or even the decision to proceed.
The pressure also reaches procurement teams, which decide how services are bought. A combined strategy and development engagement can offer clearer responsibility. It can also make it harder to separate the value of the advice from the value of the software.
Buyers should be able to identify what they receive at each stage. A strategic recommendation, a testable prototype, and a supported application are different deliverables. Treating them as interchangeable makes it difficult to judge whether an engagement has reached its intended destination.
There is a related staffing challenge for Fundamentalco. Software work continues after an executive presentation ends. Changes in source information, user needs, and underlying technology can create ongoing maintenance work. Selling development capability therefore creates obligations that extend beyond producing the initial artifact.
The same logic puts pressure on outside delivery partners. Where a consultancy develops more work internally, partners must understand which responsibilities remain theirs. A clear boundary can help collaboration. An unclear boundary can leave the client coordinating gaps between teams that each assumed someone else owned them.
None of this establishes that Fundamentalco will displace a particular competitor or systems integrator. The available evidence does not support that conclusion. The stronger judgment is about accountability: a firm that offers both direction and implementation invites assessment across both.
For enterprise buyers, that is the practical significance of the deal. They gain a potential supplier with a broader remit. They should also expect a clearer explanation of who owns testing, approval, deployment, and support when the work moves beyond consulting.
Owning the Builders Changes the Handoff
The acquisition’s strongest strategic argument is that implementation knowledge can influence the advice before a client commits to it.
A conventional handoff can separate the team defining a business direction from the team implementing it. Each group then works with a different understanding of the original problem. Combining them creates an opportunity for shared decisions, provided the organization actually changes how projects run.
Fundamentalco’s account of its AI studio integration describes an existing application for real estate clients. The company says an agent turns transformation strategy and design into sales and leasing materials. An agent is software that uses an AI model to carry out tasks within a defined workflow.
That example identifies a recognizable task rather than an undefined promise of transformation. It connects strategic choices with materials employees use in their work. However, the description does not provide an independent evaluation of accuracy, adoption, or commercial outcomes.
The distinction helps locate the opportunity. A strategy becomes operational when people can use it to make decisions or complete tasks. Generating materials can support that transition, but the usefulness of those materials still depends on their content, timing, and acceptance by the people receiving them.
For example, an application could produce a polished sales document while using an outdated property detail. This is an illustrative failure mode, not a reported incident involving Fundamentalco. It shows why development and content review belong within the same delivery conversation.
Ownership can make that conversation easier to organize. Consultants and engineers can share responsibility for deciding which information is authoritative and what requires approval. The benefit comes from the working process, however, rather than the legal structure alone.
The industry comparison is Accenture Song’s Work & Co acquisition, completed on January 22, 2024. Accenture described the transaction as an expansion of digital product and experience capabilities. That earlier deal provides a historical reference for combining advice with the ability to build.
The comparison has limits. Work & Co’s digital product business and Move38’s AI focus are not identical. The transactions do not establish equivalent scale, execution quality, or client demand. They illustrate a shared organizational choice: bringing implementation expertise closer to the business relationship.
For Fundamentalco, the relevant contest is therefore between two delivery approaches. One defines a direction and passes it to another team. The other keeps strategy and development in sustained contact as practical constraints emerge.
Neither approach wins automatically. An outside implementation partner can challenge assumptions and contribute specialist expertise. An internal studio can become overstretched or inherit decisions too late. The outcome depends on when builders participate and how much authority their findings carry.
The strongest version of the combined model makes testing part of strategic judgment. The weakest version adds a demonstration after the strategy has already been approved. Future client work should make it possible to distinguish between those models.
A Proprietary Platform Still Needs Evidence
SteelframeAI’s ownership establishes control over an asset, while its business value still requires evidence from actual use.
The word proprietary can describe software a company owns or controls. It does not, by itself, explain what makes the system distinctive. Buyers still need to understand which capabilities depend on the platform and which depend on people configuring and operating it.
The public descriptions reviewed for this acquisition do not provide enough technical detail to resolve that question. They do not offer a reproducible performance evaluation or a detailed comparison with alternative approaches. It would therefore be premature to rank SteelframeAI against other enterprise AI products.
That gap does not make the platform unimportant. It changes how its importance should be assessed. The useful questions concern the work it supports, the information it can access, and the evidence that its outputs meet the requirements of those tasks.
For an internal consulting application, retrieving a relevant past project is only part of the job. The system must also help users distinguish transferable reasoning from details that belonged to another client. Similar wording does not guarantee that an earlier recommendation fits a new situation.
This is where the acquisition intersects with knowledge management. A firm’s accumulated documents contain useful experience alongside outdated assumptions, exceptions, and material with restricted access. Connecting that archive to AI creates a continuing responsibility to maintain context and permissions.
The difference between personal and shared information is relevant here. A knowledge base comparison provides additional context for readers considering how information ownership changes across those settings. The acquisition reports do not establish how Fundamentalco’s system manages every such boundary.
A technical evaluation would also need to separate output quality from reviewer effort. An application can produce an acceptable final document because employees spend substantial time correcting it. That may still be useful, but the evaluation should capture the full workflow.
Independent research provides a reason for that caution. A Nature paper on semantic uncertainty examined a method for detecting certain AI confabulations, meaning confidently generated false content. The researchers also described limits, including errors that arise consistently.
That finding is general background, not an assessment of Move38’s software. Its relevance is that fluent output cannot serve as the sole test of correctness. A company-specific platform still needs evaluation suited to the decisions and documents it supports.
A strong disclosure would explain the task, the acceptance criteria, and the review process. It would also show where the application fails or requires human intervention. Such detail would let buyers assess practical value without needing access to confidential client material.
For now, the justified conclusion is narrower. Fundamentalco has acquired a studio and platform associated with work it already knows. Whether those assets create a repeatable advantage across different client environments remains open.
Integration Brings Responsibilities That a Demo Can Hide
A combined strategy and development business must account for data handling, reliability, and maintenance throughout the engagement.
These responsibilities are especially relevant when an application draws on earlier client work. Access to a document does not automatically establish permission to reuse its contents in every setting. The reports reviewed do not explain the full set of controls governing that reuse.
That absence is a disclosure gap, not evidence of misconduct. There is no basis here to claim that Fundamentalco or Move38 has exposed client information. There is a basis for asking how the combined business separates client material and approves its use.
NIST’s generative AI risks profile identifies issues including data privacy, information security, intellectual property, and unreliable outputs. Those categories provide general evaluation context. They do not establish that a particular problem exists in SteelframeAI.
For a buyer, the practical concern is responsibility when something changes. If an approved source document becomes outdated, someone must update the system or its supporting information. If the application produces an incorrect statement, someone must identify its cause and decide what needs correction.
A demonstration can leave those responsibilities invisible. A production application, meaning software used in everyday operations, cannot rely on them remaining informal. Users need a route for reporting problems, and the delivery team needs a process for responding.
The acquisition makes it reasonable to ask whether Fundamentalco intends to own that continuing service. Building a prototype and operating a supported application require different commitments. The public description of expanded capabilities does not settle the scope of every future engagement.
There is also an organizational risk in assuming that technical expertise will spread automatically after a transaction. Consultants need to understand what developers require. Engineers need enough access to the business problem to challenge a weak specification. Leadership must give both groups time to work together.
Otherwise, an internal studio can reproduce the same handoff problems that an external partnership faced. The reporting line changes while the project process stays largely the same. That is why integration deserves attention as a delivery question rather than a matter of branding.
Commercial claims need similar care. The acquisition coverage does not disclose transaction terms or independently establish client financial gains. There is no sound basis for calculating a return on the deal or attributing broader company performance to it.
A fair assessment can hold both points together. Fundamentalco has gained a more direct route to technical implementation. It has also taken on the task of showing that broader ownership produces dependable work. Neither the opportunity nor the uncertainty should erase the other.
For clients considering the combined offer, the most useful distinction is between a promise about future capability and a commitment attached to a specific deliverable. Clear scope and responsibility make that distinction assessable before a project begins.
Watch Deployment, Repeat Use, and Delivery Economics
The next evidence should show what clients use, whether they keep using it, and what support the work requires.
The first signal to watch is a client deployment described with enough detail to understand the change. A useful account would identify the original task, the application introduced, and the people using it. A client’s confirmation would add weight to the supplier’s description.
That evidence would strengthen the argument that the acquisition connects strategy with implementation. Another prototype announcement would demonstrate development activity, but leave everyday use unresolved. The difference matters because a working demonstration and a working service face different demands.
The second signal is repeat use beyond the initial launch. Continued use would suggest that the application fits a recurring need. Evidence of substantial abandonment or work returning to the previous process would weaken that interpretation.
Repeat use should also be considered alongside quality. Employees might use an application because it is required, while still correcting much of its output. A meaningful account would therefore describe both participation and the review needed to reach an acceptable result.
The third signal is delivery economics, meaning the resources required to build, review, and maintain the work. This does not require public contract terms. An anonymized case study could explain changes in staff effort, correction work, and ongoing support.
That disclosure would help distinguish a reusable capability from a service requiring extensive custom effort each time. Both can serve clients, but they imply different limits on how the combined organization grows. Buyers benefit from knowing which model supports the proposed engagement.
These signals should be read in sequence. Deployment establishes that something reached users. Repeat use establishes that it continues to serve a purpose. Delivery economics helps explain whether providing that purpose remains practical for the supplier and client.
Fundamentalco acquires Move38 with an existing collaboration as its starting point. That gives the transaction more substance than an announcement built entirely around future intentions. It also creates a useful comparison: what changes after the studio becomes part of the consultancy?
Over the coming months, watch for client-confirmed applications and descriptions of how teams use them. Look for evidence of continued use, human review, and support after launch. Those details would make the acquisition’s value easier to assess than another broad statement about transformation. If you are evaluating a combined strategy and AI development engagement, ask the supplier to connect its proposed direction with a specific deliverable. Identify who will approve the output, maintain the application, and respond when it fails. Then ask what evidence would justify continuing the work. Which part of your proposed engagement has a clear owner today, and which part still exists only as a promise?



