1(globalThis.TURBOPACK||(globalThis.TURBOPACK=[])).push(["object"==typeof document?document.currentScript:void 0,48086,e=>{"use strict";let t={src:e.i(15726).default,width:600,height:410,blurWidth:8,blurHeight:5,blurDataURL:"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAFCAYAAAB4ka1VAAAAsElEQVR42gGlAFr/AKW0w/+0x9r/maGt/6m8zf+lusv/ssfX/8HU5P+lusj/AISIjv+Do8D/XXeT/77Q4v/Eztn/qLXA/7fJ0/+If3j/AGFxff9ObIj/XXya/5y2yv+ZrsD/boeh/4GirP92eHr/AC5BTf9CWGn/dIST/4Gds/94nb3/SnOe/05ofv8oSGj/AENYZv+Cmaz/boaY/4OWqf+JnbP/k6a8/5mouv98lq//815uFnNKE2AAAAAASUVORK5CYII="},a={src:e.i(21214).default,width:1280,height:906,blurWidth:8,blurHeight:6,blurDataURL:"data:image/jpeg;base64,/9j/4AAQSkZJRgABAgAAAQABAAD/wAARCAAGAAgDAREAAhEBAxEB/9sAQwAKBwcIBwYKCAgICwoKCw4YEA4NDQ4dFRYRGCMfJSQiHyIhJis3LyYpNCkhIjBBMTQ5Oz4+PiUuRElDPEg3PT47/9sAQwEKCwsODQ4cEBAcOygiKDs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwCnqUYttGeY8LGpdFQD5WOMY46VGl1c0S91n//Z"},i={src:e.i(95935).default,width:1280,height:853,blurWidth:8,blurHeight:5,blurDataURL:"data:image/jpeg;base64,/9j/4AAQSkZJRgABAgAAAQABAAD/wAARCAAFAAgDAREAAhEBAxEB/9sAQwAKBwcIBwYKCAgICwoKCw4YEA4NDQ4dFRYRGCMfJSQiHyIhJis3LyYpNCkhIjBBMTQ5Oz4+PiUuRElDPEg3PT47/9sAQwEKCwsODQ4cEBAcOygiKDs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDDgebWry0nvJ5GTylZowRyT15xxWc3bQ2pxur3P//Z"},n={src:e.i(83188).default,width:1280,height:853,blurWidth:8,blurHeight:5,blurDataURL:"data:image/jpeg;base64,/9j/4AAQSkZJRgABAgAAAQABAAD/wAARCAAFAAgDAREAAhEBAxEB/9sAQwAKBwcIBwYKCAgICwoKCw4YEA4NDQ4dFRYRGCMfJSQiHyIhJis3LyYpNCkhIjBBMTQ5Oz4+PiUuRElDPEg3PT47/9sAQwEKCwsODQ4cEBAcOygiKDs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7Ozs7/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDnrjXb2G0GwplgDnaM8jpWhjY//9k="},o=[{id:"the-gap-between-ai-spend-and-ai-results",date:"Jun 6, 2026",author:"By Manos Tzagkarakis, Engineering Lead at Datawise.ai",title:"The Gap Between AI Spend and AI Results",teaser:"A pattern repeats in almost every conversation we have had with prospective clients over the last year. They have spent a meaningful amount of money on AI subscriptions, on copilots, on chatbots, on a handful of proofs of concept. Some of these investments came from vision, others from a perfectly reasonable fear of being left behind. What is consistently missing is not effort or budget, it is results. Or more precisely, the kind of results that can be defended to a board, to a finance team, or to a customer, with numbers attached.",paragraphs:["This is not only our observation. <a href='https://www.ibm.com/thought-leadership/institute-business-value/en-us/c-suite-study/ceo' target='_blank' rel='noopener noreferrer'>IBM's 2026 CEO Study</a> reports that nearly 80% of executives expect AI to drive significant revenue by 2030, but only 24% know where that revenue will come from. <a href='https://www.deloitte.com/us/en/wh
1at-we-do/capabilities/applied-artificial-intelligence/content/state-of-ai-in-the-enterprise.html' target='_blank' rel='noopener noreferrer'>Deloitte's 2026 State of AI survey</a> puts a finer point on it: only 20% of organizations report actually achieving revenue growth from AI, while 74% say they hope to. The expectation is in place, the path to it is not. There is also a useful paradox worth naming: the companies building AI are simultaneously the ones investing most aggressively in human consulting partnerships. Anthropic, to take one example, is actively recruiting partner success managers and building ecosystems of consultancies and systems integrators around Claude. If the technology could deploy itself into organizational reality, none of that investment would make sense.","This is the conversation we keep ending up in, and it is the one we want to write down here. To describe how we envision AI transformation when we walk into a client's context, what we typically find, and how we try to start them on something that produces concrete outcomes, then help them expand from there into more areas of the business. The internal politics and power structures are theirs to handle. We adapt the technology around those.","<span class='text-2xl font-bold'>1. The two outcomes that actually justify the spend</span>","When clients describe what they want from AI, we hear two distinct kinds of expectation, and they are worth separating because they require different engineering postures.","The first is cost reduction. This is the older, more intuitive narrative. Automate work that humans currently do, and pay less for it. Customer support, document processing, internal search, manual data entry. These remain perfectly legitimate goals, and they often produce the easiest wins to measure, because the baseline already exists. You know what one ticket costs to resolve today, and you can compare.","The second expectation is newer and, in our experience, the more interesting one. It is about new revenue and new capabilities, things that simply were not feasible before AI made them tractable. An airline using agents to rebook flights and reroute bags automatically, freeing human agents for the complex cases that actually need judgment. Decision support inside workflows where having an analyst in the loop was previously impossible. Products that shape themselves around customer context in ways that used to require a custom build per account. This is the part of AI transformation that is not just about doing the same things more cheaply, it is about doing things that did not exist on the menu before.","We see many clients spend heavily on the first kind of outcome, and some are now starting to wonder how they can move on to the second pillar, as the AI infrastructure around them gets more mature. Part of our work is helping them see that the cost cutting story, while useful, is not the ceiling. The new revenue story is harder to scope, harder to estimate, and harder to deliver, but it is also where the meaningful advantage usually lives. Before clients can pursue either outcome seriously, there is a mental model that usually needs to shift first.","<span class='text-2xl font-bold'>2. Chatbots are not the current frontier</span>",'When a non-technical stakeholder thinks about AI, the first-hand experience they usually have is a chatbot. Sometimes it is an agent in one of its more accessible, ready-made forms, a code assistant or a desktop LLM client, but they very rarely have hands-on experience with a true agent, one with its own harness, system integration, tool capabilities, and real autonomy, in the way they do with chatbots. That is the artifact they have used, the artifact they have shown to their colleagues, the artifact they will reference when they say "we should do something like that." This is not a criticism, it is just the calibration that comes from what is widely deployed and easy to try.',"Part of what we end up doing in early conversations is gently reframing this picture. The current state of the art is not a chatbot, it is an agent, or more often a small system of agents working together, implementing a workflow by chaining simple actions and responsibilities together. The difference is not cosmetic. A chatbot answers. An agent acts. An agent can call tools, retrieve information, take steps, ask for confirmation, and bring something back while being evaluated at various levels. A chatbot keeps a conversation going. An agent ends a task and ideally accomplishes an outcome.","This distinction matters because it changes what AI can be put in charge of. The ec
1onomic argument shifts. Chatbots compress the cost of answering. Agents compress the cost of doing. The second one is where most of the new revenue and new capability stories actually live. Another way to think about it is that every major infrastructure shift follows the same pattern: the raw technology lands and while impressive it does not transform anything. The applications built on top of it do. Electricity needed appliances, the internet needed software, AI needs workflows and agents. Having access is not the same as using it productively.","That said, agents are not a clean win. They also fail, and they fail in ways that are harder to detect than traditional software failures. <a href='https://www.gartner.com/en/newsroom/press-releases/2026-05-26-gartner-says-applying-uniform-governance-across-ai-agents-will-lead-to-enterprise-ai-agent-failure' target='_blank' rel='noopener noreferrer'>Gartner predicts that by 2027, 40% of organizations will demote or decommission AI agents</a> because of governance struggles. The root cause is that most organizations treat agent governance as binary, either fully locked down or fully trusted. Over-restriction slows delivery and drives shadow development. Under-restriction increases operational and compliance risk. Only one in five companies, <a href='https://www.deloitte.com/us/en/what-we-do/capabilities/applied-artificial-intelligence/content/state-of-ai-in-the-enterprise.html' target='_blank' rel='noopener noreferrer'>according to Deloitte</a>, has a mature governance model for autonomous agents. This is not an argument against agents, it is an argument for building them with observability, guardrails, evals, and proportional governance from the start. Which is where engineering comes in.","<span class='text-2xl font-bold'>3. Where engineering becomes a build, not only a slide deck</span>","Agents that work in demos and agents that work in production are not the same thing. There is a part of AI transformation where consulting and slideware stop being enough, and you need actual engineering. We bring two things into that part of the engagement.","The first is depth in offline models and reinforcement learning training. Not every problem is best served by a hosted frontier model accessed over an API. Many of our clients have data they cannot send off premise, latency budgets that public APIs cannot meet, or economics that fall apart at scale unless inference is local, tuned, and operates at a justifiable cost. For those cases, we work on smaller, specialized models, on fine tuning and reinforcement learning approaches, and on the operational machinery to keep them honest in production. This is not a religious position about local versus hosted, on the contrary it is a position that the right answer depends on the workload and what the customer actually needs. The fact that we can do both gives us an edge.","The second is Evolvable.ai, our agent orchestration platform. We built it because we were repeatedly running into the same pattern at clients, a few standalone bots, a few scripts, a RAG pipeline, a few workflow automations, none of them aware of each other, all of them losing context at hand-offs. Evolvable.ai gives us speed. Bring-your-own-key model access, customized offline models, built-in observability, tenant isolation, and human-in-the-loop controls are already solved problems inside the platform, which means we are not rebuilding orchestration infrastructure from scratch on every engagement. That is the advantage, time to first working agent, not platform lock-in.","Solving the engineering part though is only half of the problem. Once agents start completing tasks, things start to shift in how the organization works. In the pre-AI era, tasks and people were welded together. Managing people was how you managed work, and the proxy held. In the agentic era, that proxy is starting to break. Task outcomes can be monitored directly, fast, with timing, evidence, and clear records of success or failure. This close monitoring of people, especially in more creative industries, does not have the same results. Recent research points the same direction: <a href='https://arxiv.org/abs/2510.25137' target='_blank' rel='noopener noreferrer'>MIT's Iceberg Index</a> proposes measuring AI exposure at the task and skill level rather than the job level, precisely because traditional people-centered metrics cannot see where the real overlap between human and AI capability occurs. The implication is that leaders need different instruments for each: observability and guardrails for task pipelines, trust and judgment for the people who design, supervise, and improve them.","<a href='https://www.gartner.com/en/newsroom/press-releases/2026-05-05-gartner-says-autonomous-business-and-artificial-intelligence-layoffs-may-create-budget-room-but-do-not-deliver-returns' target='_blank' rel='noopener noreferrer'>Gartner's May 2026 research</a> confirms this as well, the organizations improving ROI from autonomous technologies are not those eliminating people, but those investing in skills, roles, and operating models that allow humans to guide autonomous systems. A downstream effect we are already observing is that team structures flatten because scope-of-contribution broadens. More people can touch more parts of the work, and the skills that rise in value are taste, judgment, and the ability to frame problems well enough that another person, or an agent, can understand and act on them.","<span class='text-2xl font-bold'>4. How we start</span>","Everything above describes what we know and what we can build. None of it matters if we cannot prove it in a client's actual context. This is why we never start with a large commitment.","When we engage with a client, we ask them a simple question: which problem can we solve first to display value, for which user, with which constraints, and how will we know it worked. We choose something small and doable. Not a demo on someone else's data, not a slide. We are looking to identify a specific situation where an agent can start doing a real piece of their work, end to end, with the rough edges visible.","For task automation specifically, we instrument three things before we begin: the baseline cost or time of the current process, the same metric after the agent is running, and the error or escalation rate that tells us whether quality held. If we cannot define those three before the engagement starts, we treat the problem as not yet ready for AI. Conway's law is real after all, systems end up reflecting the communication structures of the organizations that build them, and AI architectures are no exception. This is why we shape the engagement around the organization as it actually exists, not as we wish it were.","That early win is how we earn the trust that our way of working produces tangible benefits, before scope expands into anything larger.","<span class='text-2xl font-bold'>5. The cost of not starting</span>","The organizations that delay this work do not stay still. They accumulate disconnected AI tools, uncoordinated agents, and organizational assumptions that were designed for a world where tasks and people were the same thing. <a href='https://www.gartner.com/en/newsroom/press-releases/2025-08-26-gartner-predicts-40-percent-of-enterprise-apps-will-feature-task-specific-ai-agents-by-2026-up-from-less-than-5-percent-in-2025' target='_blank' rel='noopener noreferrer'>Gartner projects task-specific AI agents will jump from less than 5% of enterprise applications in 2025 to 40% by the end of 2026</a>. The question for most organizations is no longer whether agents will arrive in their workflows, it is
1whether they will arrive in a structured and controllable way, with governance, measurement, and intent, and thus helping businesses achieve their goals, or whether they will arrive chaotically, leading to distrust, skepticism, and eventually rejection.","Each quarter that passes without addressing this makes the eventual changes more challenging. Not because the technology gets harder to embrace, but because the communication lines, the structures, and the expectations calcify around old assumptions and habits. By the time the gap between what the tools can do and how the organization uses them becomes visible, it is already a harder problem to solve.","If you want to pressure-test where you are, we can usually tell within a single working session whether your current AI investments are producing measurable outcomes or whether the measurement apparatus itself is missing. That session costs nothing except honesty about what has actually worked so far."],imageUrl:"/images/gap.png",image:{src:e.i(91576).default,width:1376,height:768,blurWidth:8,blurHeight:4,blurDataURL:"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAAECAYAAACzzX7wAAAAfklEQVR42g3DTQuCMACA4f39gs5Ft4QoSZhTM7+aU1rsMCIFqUPdgn7GW4dH2FrSyxXhZo2pUm7e8ZiGv5
1Hv542o1I4oWLKYzanzGHvpaRqNSnKmwSPsOSOJtqgwwHUlr+eIbg2HSKHrAnHVGV0pOcV72kJy9xZnDXmWUhxjfjvHZeSAMBMmAAAAAElFTkSuQmCC"}.src},{id:"ai-augmented-development-demands-from-your-organisation",date:"Mar 4, 2026",author:"By Manos Tzagkarakis, Engineering Lead at Datawise.ai",title:"What AI-Augmented Development Demands from Your Organisation",teaser:"The cost of producing working code has been falling for years, and AI coding tools have accelerated that trend dramatically. We do not yet know where the floor is. A single developer, assisted by AI agent(s), can now produce in hours what once took a team days. Multiple agents working in parallel can generate volumes of code that would have been unthinkable just two years ago. And yet, producing more code faster has not automatically translated into delivering better software or business value. What we are seeing instead is that organisations with existing structural weaknesses keep wondering why they cannot harvest those productivity gains. That tells us something important about what AI actually improves, and what it does not.",paragraphs:["<span class='text-2xl font-bold'>1. The Distinction Between Code and Engineering</span>","Mediocre software organisations tend to produce tons of code and little engineering. That was tolerable and even economically rational, especially when the requested rate of change was slow. You could ship a version that worked, patch it when something broke, throw additional developers at it when things got complicated, and rewrite the whole thing every few years when the accumulated mess became unmanageable. The resulting software might have been working in the narrowest sense: the current version did what was specified. But it almost always lacked the qualities needed to keep evolving at a predictable pace, mostly due to a lack of clear boundaries, meaningful test coverage, operational visibility and the ability to change one part of the system without breaking others.","That was the implicit bargain: low upfront cost, high long-term cost. Many organisations accepted it â sometimes knowingly, sometimes not.",'AI has fundamentally disrupted that process. When the cost of generating code drops toward zero, "cheap code" is no longer a competitive advantage. What remains, what always remained, is the engineering underneath: the design decisions, the structural boundaries, the feedback loops, the operational readiness. So the organisations that invested in those things, both in technology and in cultivating their people, now find that AI amplifies their capabilities. On the contrary, the organisations that did not invest in those things usually discover that AI amplifies their dysfunction at worst or observe moderate benefits at best: more code, produced faster but with the same architectural weaknesses, the same lack of testing discipline and the same inability to deploy safely. The mess compounds at machine speed.',"This is how we think about it at Datawise: GenAI-based software development is an amplifier of organisational capabilities, not a replacement for good engineering principles. It c
1an make high-performing organisations even better and make low-performing organisations worse.","<span class='text-2xl font-bold'>2. The Skills AI Cannot Replicate (yet at least...)</span>","If code generation is increasingly commoditised, the natural question is: what do experienced engineers actually bring to the table?","At Datawise, we have been working with different clients and paradigms long enough to have a clear opinion on what patterns matter most. The engineers who thrive are not the ones who memorised the most API signatures or knew every IDE keyboard shortcut (although these can still matter for maintaining flow). They are the ones who carry something far harder to automate: judgment, adaptability, and the ability to turn business intent into engineering decisions.","Judgment is knowing when to introduce an architectural boundary, not just how. It means recognising that a system is losing optionality, that the next feature is going to be harder than the last one, and deciding to act before the cost compounds. It is the sense of timing and taste that tells you this refactoring matters now, or that this abstraction is premature. To paraphrase Kent Beck, whose thinking on software design has shaped much of what we practice: 90% of what developers used to pride themselves on, the mechanical execution skills, simply does not matter as much when AI enters the picture. But the remaining judgment layer has become dramatically more valuable, because you are making those kinds of decisions so much more frequently.","There are specific human capabilities that we see carrying outsized leverage in AI-augmented teams:","<ul>","<li class='ml-4'><b>Design taste and optionality recognition.</b> The ability to look at generated code and immediately sense whether it is heading toward a maintainable system or toward a slow, compounding mess. The ability to see options, structural choices that make the next change easier, and weigh them against the pressure to ship features. AI compresses timelines, which means these optionality decisions arise multiple times a day instead of once a sprint.</li>","<li class='ml-4'><b>Testing instincts.</b> Not only writing tests (AI can do that). But knowing what to test, when to expand testing coverage, why, what are the tangible benefits that testing brings to both the engineering team and the organisation. It also means recognising when a coverage gap represents a real risk versus noise. Furthermore, more advanced testing techniques â such as mutation testing or property-based testing, which were rarely applied by senior engineers because of their implementation cost, can now be applied far more frequently. The critical skill is recognising the moment when each technique is the right response. As we have observed, the skills we developed through practices like TDD, or thinking proactively before writing code, or thinking through what could go wrong or what we want to prove or disprove, remain fully valid even when we are not handwriting every test.</li>","<li class='ml-4'><b>Curiosity as a practised discipline.</b> AI provides an infinitely patient, contextually aware tutor. The engineers who grow fastest are the ones who notice a gap in their understanding during real work and fill it immediately, asking the AI to explain a technique it suggested, questioning trade-offs, exploring alternatives. That curiosity compounds over time into deeper judgment.</li>","<li class='ml-4'><b>Communication, prioritisation, and the ability to say no.</b> Developers have always been a bridge between the business requirement and the working system. That translation, taking a vague customer need and producing something that genuinely meets it, does not change because the code is generated differently. And because AI compresses feedback loops, the ability to gather feedback, absorb it, slice scope, and communicate trade-offs becomes proportionally more important. These are the skills we exercise way more often now.</li>","<li class='ml-4'><b>Confidence and Trust in what we build.</b> Perhaps the most underrated skill of all. Confidence that when things change, and they will keep changing, you have the capacity to learn or adapt to the next thing, the next requirement, the next technology, and so on. That assurance is not innate. It is built through practice, through having navigated paradigm shifts before, and it transfers across every transition this industry has been through.</li>","</ul>","These are not new skills. But AI has made their presence or absence visible almost immediately.","<span class='text-2xl font-bold'>3. Architectural Readiness: The Characteristics That Actually Matter</span>","If human judgment is the first pillar, the second is the architecture those humans design and the AI operates within.","At Datawise, we frame architectural readiness through what the industry increasingly recognises as fast flow architecture, a set of principles designed to optimise the speed and safety of moving changes from idea to production, while supporting continuous learning and improvement, as described by Chris Richardson in his book Microservices Patterns. Richardson's work on this topic mirrors what we have concluded from our own practice: the architecture must satisfy five quality attributes, and each one becomes more critical, not less, when AI agents enter the picture.","<ul>","<li class='ml-4'><b>Modifiability:</b> the ability of the team to respond to changing requirements. Things that change together belong together (High Cohesion), and things that do not, should not be entangled (Low Coupling). When a system is designed this way, functionality maps to well-defined areas of the codebase. The engineer or AI agent can focus on that area without tracing dependencies across the entire application, and there is less extraneous code to reason about. For AI-augmented development, this matters directly: less unrelated code in the context window means fewer tokens, higher accuracy, and fewer unintended side effects. You can now force the agent to work inside boundaries. Without this characteristic, agents are forced to reason about large, tightly coupled sections of the system, amplifying existing architectural coupling rather than accelerating delivery. Practices from Domain-Driven Design, such as identifying bounded contexts and defining explicit module contracts, are among the most effective tools for achieving modifiability in practice.</li>","<li class='ml-4'><b>Evolvability:</b> the ability to upgrade the application's technology stack incrementally rather than as a system-wide event. In a well-decomposed architecture, whether that is a modular monolith or microservices, most technology decisions can be made per component. For AI-augmented development, this reduces the blast radius of technology changes to a single component. Without evolvability, even small upgrades have system-wide impact. Evolvability also protects the organisation's investment and allows the system to adopt new technologies over time without requiring a full rewrite, especially as the AI tooling landscape continues to evolve.</li>","<li class='ml-4'><b>Testability:</b> the ability to verify that a change is releasable through fast, automated tests that run locally. This is critically important for AI-augmented development because tests are effective guardrails for coding agents. They define what correctness means and force agents to make progress through verifiable steps rather than speculative code generation. Without testability, agents generate changes faster than the organisation can verify them. CI becomes a bottleneck. The first real signal that something is wrong comes from production, and by then the cost of fixing it has multiplied.</li>","<li class='ml-4'><b>Deployability:</b> the degree to which getting a change into production is automated, predictable, and safe. It is one where no person needs to perform tons of manual steps to release a change, and the deployment pipeline handles building, testing, packaging, and releasing automatically. A human's role shifts from executing the deployment to monitoring it, getting notified when something goes wrong, and having the controls to roll back if needed. When deployability is high, the rate of change can increase without increasing operational burden. Notably, achieving high deployability is itself a domain where AI agents can contribute significantly, helping teams build and refine the automation, pipeline configuration, and infrastru
1cture-as-code that make safe, hands-off deployments possible.</li>","<li class='ml-4'><b>Observability:</b> the ability to understand how the system and its users are actually behaving, not after an incident, but continuously and in near real-time. Observability provides the means of understanding how real users interact with the system, what effects those interactions have, and whether a deployment was successful. This connects directly to one of the core principles of agile delivery: fast feedback loops. Without that signal, teams are flying blind and corrective actions are delayed.</li>","</ul>","AI knows these characteristics. It knows how to implement them. What AI does not know is how much of each one your specific organisation actually needs and can sustain, and this is where the judgment of teams who have calibrated these decisions for real organisations, not theoretical ones, becomes even more valuable.","<span class='text-2xl font-bold'>4. The Missing Variable: Organisational Maturity and Conway's Law</span>","The conversation about AI-augmented development usually stops at technology. We believe it shouldn't.","Conway's Law tells us that systems reflect the communication structures of the organisations that build them. At Datawise, we take this further: custom software built for a client must match the operational capabilities of that client's organisation. Software is not independent of what the client can support.","Consider a concrete example. You can build a large distributed system with every modern best practice applied rigorously â microservices, comprehensive monitoring and alerting, automated scaling, sophisticated observability, blue-green deployments, the full apparatus of operational excellence. If you deliver that system to a small organisation with a handful of engineers and no dedicated operations team, several things happen. In the worst case, they lose control of the software entirely; they cannot debug it, cannot deploy it confidently and cannot respond to incidents at the speed the business demands. In the more common case, they lose adjustability. As architectural scale increases, the ease of making changes decreases. The system becomes rigid precisely because it was designed for a level of operational and decision-making maturity the organisation does not possess. And the cost of operating it, even if they manage to do so, exceeds what the system's value justifies.","That is not good engineering. That is over-engineering dressed up as quality.","Maturity is not only a software property. It is an organisational one. The right architecture is the one that matches the client's current operational reality, their growth trajectory, and the rate of change their business actually demands: not just their operational capabilities, but their capacity to make and stand behind the architectural trade-offs the system imposes. A system designed for high scalability trades away flexibility. That trade-off is valid, but only if the organisation understands it, factors it into business risk, and is prepared to live with the constraints. The right architecture is calibrated to these realities, not the one that scores highest on a theoretical checklist. A well-designed modulith with clear domain boundaries and solid test coverage, operated by a team that understands it thoroughly, will outperform an over-architected distributed system that the same team cannot safely or quickly alter or meaningfully observe.","This is the variable that AI cannot solve for. An AI agent can implement any architectural pattern you ask for. It cannot tell you whether your organisation is ready to own the result.","<span class='text-2xl font-bold'>5. Why Datawise Builds Partnerships, Not Just Software</span>","This is why Datawise operates as a long-term technical partner, not just as a code shop. We do not just write software for our clients; we form partnerships precisely because the right system requires understanding two things that cannot be captured in a specification document: where the organisation is today, and where it wants to go.","Our clients utilise Datawise's experience not just in
1writing software, but in understanding how software works within an organisation. How it gets deployed. How it gets monitored. How changes flow through teams. How operational capabilities constrain or enable architectural choices. We translate that understanding into systems that fit the client's current needs and structure, without over-engineering (and so overpaying) while at the same time supporting change and accommodating their vision for what they want to become.","The software aspect of their organisation grows with them. Not ahead of them, leaving them unable to operate what was built. Not behind them, forcing rewrites when the business outgrows the architecture. With them â calibrated to their reality, with the path open for evolution.","AI has made this kind of partnership more valuable, not less. When generating code is trivially cheap, the differentiation shifts entirely to judgment: what to build, how much complexity is warranted, which architectural qualities matter at this stage of the client's maturity, and how the system should evolve as the organisation grows. That judgment comes from experience, from doing this for client after client, from having seen what happens when the system outpaces the organisation, and when the organisation outpaces the system.","If your organisation is navigating this shift or wondering whether the software you want today will still serve your business in two years, we would welcome that conversation. Reach out to us at Datawise.ai."],imageUrl:"/images/ai-dev.jpg",image:n.src},{id:"healthy-software-organizations-flow-metrics-dx",date:"Dec 29, 2025",author:"By Manos Tzagkarakis, Lead Engineer at Datawise.ai",metaTitle:"Healthy Software Organizations: Flow, Metrics & DX",title:"Helping Build Healthy Software Organizations: Flow, Metrics, and Developer Experience at Datawise.ai",teaser:"Over the past decade, the software industry has learned a hard truth: you can have excellent engineers, modern cloud infrastructure, and the latest frameworks, and still struggle to deliver meaningful change quickly. What separates consistently highâperforming organizations from the rest is not a specific technology choice, but how teams, architecture, and workflows are designed to support a consistent and predictable rate of change.",paragraphs:["In practice, this comes down to three things working together:","<ul>","<li class='ml-4'>Small, focused teams with clearly owned responsibilities and boundaries.</li>","<li class='ml-4'>An architecture that can evolve as the organization grows.</li>","<li class='ml-4'>A frictionless developer experience, measured and guided by meaningful metrics such as DORA and SPACE.</li>","</ul>","This article explores how these elements fit together, and how we at <b>Datawise.ai</b> use them to create environments where teams and the products they build can thrive.","<span class='text-2xl font-bold'>Flow First: Why Structure Matters More Than Tools</span>","Most software organizations grow in a very similar pattern: a few engineers build a prototype, it succeeds, more people join, departments form, and gradually the system becomes harder to understand. Delivery slows down.",'<span class="ml-4">"We need microservices."</span>','<span class="ml-4">"We need Kubernetes."</span>','<span class="ml-4">"We need a new CI/CD platform."</span>',"Those are the kinds of solutions people quickly propose, and although all of them can be useful, they are rarely the root cause. The real constraint is usually <span class='font-bold'>how information flows through the organization</span>:","<ul>","<li class='ml-4'>Who is responsible for what?</li>","<li class='ml-4'>How many handâoffs happen before a change reaches production?</li>","<li class='ml-4'>
1How often do teams need meetings just to coordinate everyday work?</li>","<li class='ml-4'>How effective are those meetings?</li>","</ul>","When responsibilities are scattered across functional silos (different backend teams, frontend teams, QA teams, Ops teams), every change becomes a miniâproject in coordination. In contrast, when small, crossâfunctional teams own a wellâdefined stream of work endâtoâend, they can move faster, learn quicker, and take real ownership of outcomes.","Frameworks such as Team Topologies have popularized this idea: align teams around streams of value, reduce unnecessary dependencies between them, and support them with specialized teams where it makes sense. The key is not the label, but the intentional design of team boundaries and interactions. This, in turn, is tightly connected to the technical aspects of how software is architected, built and operated.","<span class='text-2xl font-bold'>Measuring What Matters: DORA as the Fitness Test for Flow</span>","Designing for flow is one side of the coin. The other side is measuring whether the system is actually healthy. This is where the DORA metrics play an important role:","<ul>","<li class='ml-4'>Deployment Frequency â how often do we ship to production?</li>","<li class='ml-4'>Lead Time for Changes â how long does it take from code committed to code running in production?</li>","<li class='ml-4'>Change Failure Rate â what percentage of deployments cause incidents or require rollback?</li>","<li class='ml-4'>Mean Time to Restore â how quickly can we recover from a failure?</li>","</ul>","These metrics give an honest view of the system's ability to deliver change. They are not just DevOps vanity numbers; they reflect how well structure, architecture, and people are working together.","A team structure that looks great on paper but results in deployments every three weeks and long lead times is not doing its job. A beautiful architecture with tangled ownership and slow reviews will still show up in DORA as low deployment frequency and high lead time.","At Datawise, we treat DORA as the fitness test for flow:","<ul>","<li class='ml-4'>When we change how teams are shaped, we watch DORA.</li>","<li class='ml-4'>When we invest in tooling and pipelines, we watch DORA.</li>","<li class='ml-4'>When we restructure architectureâfrom monolith, to modular monolith, to more distributed designsâwe watch DORA.</li>","</ul>","The numbers don't tell the whole story, but they quickly reveal whether a change is helping or introducing new friction. Continuous feedback has always been one of the most important aspects of the Agile way of thinking and working, even if the term hasn't been in the spotlight lately.","<span class='text-2xl font-bold'>Beyond Output: SPACE and the Human Side of Engineering</span>","DORA focuses on the system's ability to ship changes. The SPACE framework complements this by looking at the human side of engineering performance:","<ul>","<li class='ml-4'>Satisfaction and wellâbeing</li>","<li class='ml-4'>Performance</li>","<li class='ml-4'>Activity</li>","<li class='ml-4'>Communication and collaboration</li>","<li class='ml-4'>Efficiency and flow</li>","</ul>","SPACE reminds us that productivity is not just about how many pull requests are merged. It's about how it feels to work in the system every day:","<ul>","<li class='ml-4'>Are developers constantly fighting flaky tests and slow pipelines?</li>","<li class='ml-4'>Do they get meaningful time in flow, or are they interrupted by handâoffs and unclear ownership?</li>","<li class='ml-4'>Do they have the tools and autonomy to solve problems, or are they blocked by process and permissions?</li>","</ul>","A frictionless developer experience is not something that should be considered optional. It is a force multiplier. Teams that enjoy working in the system, that trust their pipelines, that enjoy working with their coworkers and stakeholders, and that can see the impact of their work tend to:","<ul>","<li class='ml-4'>Ship more frequently.</li>","<li class='ml-4'>Respond faster to change.</li>","<li class='ml-4'>Build better quality into the product.</li>","</ul>","SPACE gives us language and structure to talk about this explicitly. It connects the subjective experience of engineers with tangible outcomes in the product and the organization.","Put differently: flow, metrics, and developer experience are three views of the same system. You can't optimize one in isolation for long.","<span class='text-2xl font-bold'>Architecture as a Maturity Journey, Not a Destination</span>
1","Architecture is where many organizations start the conversation, but in reality it is part of a maturity journey, not a fixed target. That journey is not only about how many deployables you have, but also about how deeply you understand your domain and how well your design reflects that understanding.","For many products, the path looks something like this:","<ul>","<li class='ml-4'>Monolith â a single codebase and deployment, often the fastest way to start and prove that an idea is valuable.</li>","<li class='ml-4'>Modular Monolith â still one deployment, but structured around business subdomains rather than technical layers, improving clarity, testability, and ownership.</li>","<li class='ml-4'>More Distributed Architectures (including microservices and eventâdriven systems) â separate deployable units where boundaries are stable, ownership is clear, and there is a real need for independent scaling, resilience, and evolution. At this stage, what is mostly at stake is the ability to scale teams, increase their independence and scale infrastru
1cture.</li>","</ul>","Along this journey, design techniques become just as important as the runtime architecture:","Practices from DomainâDriven Design (DDD) help you discover and name subdomains, bounded contexts, and the relationships between them. That gives you a language for deciding where to draw boundaries before you decide how to implement them.","Event storming and similar collaborative workshops bring business and engineering together to map flows, events, commands, and policies endâtoâend. They uncover hidden complexity, surface integration points between teams, and highlight where asynchronous, eventâdriven communication makes sense.","The mistake is to jump straight to microservices or eventâdriven architectures without first building this shared understanding of the domain and without the organizational maturity to support them. Distributed designs introduce network calls, eventual consistency, and more failure modes. They pay off when you already have:","<ul>","<li class='ml-4'>stable, clearly owned slices of functionality,</li>","<li class='ml-4'>a shared domain language and explicit boundaries,</li>","<li class='ml-4'>crossâfunctional teams with endâtoâend responsibility,</li>","<li class='ml-4'>solid automation, observability, and testing,</li>","<li class='ml-4'>and the discipline to keep services and integrations loosely coupled.</li>","</ul>","In other words, architecture should follow organizational maturity, DORA and SPACE outcomes, and the lived experience of teams, not lead them. Techniques like DDD, event storming, and eventâdriven design are part of that maturity: they help you identify problems before it is too late and make better decisions about where to invest in complexity and where to keep things simple.","<span class='text-2xl font-bold'>Frictionless Developer Experience: Where Everything Meets</span>","If team boundaries, architecture, and metrics are the conceptual pillars, the developer experience (DX) is where it all becomes tangible.","A healthy developer experience feels like this:","<ul>","<li class='ml-4'>Local environments are easy to spin up; you can run and test your slice of the system without wrestling the entire stack.</li>","<li class='ml-4'>Pipelines are fast, reliable, and visible; a commit quickly shows you whether your change is safe.</li>","<li class='ml-4'>Observability is builtâin, not bolted on; logs, metrics, and traces make it easy to understand what's happening in production.</li>","<li class='ml-4'>Common patterns are standardized; teams don't reâsolve logging, security, or configuration for every service.</li>","<li class='ml-4'>Ownership is clear; when something breaks, the team knows it's theirs and has the tools and authority to fix it.</li>","</ul>","DX is where DORA and SPACE intersect:","<ul>","<li class='ml-4'>Better DX reduces cognitive load and improves satisfaction (SPACE),</li>","<li class='ml-4'>which leads to smoother flow and better delivery performance (DORA).</li>","</ul>","This is also where ideas often associated with platforms and internal developer portals come in: reusable templates, shared libraries, selfâservice infrastructure, and wellâdesigned paved paths and information sharing mechanisms that make the right thing the easy thing.","<span class='text-2xl font-bold'>How We Apply This at Datawise.ai</span>","At Datawise.ai, we design our work environments and client engagements around these principles.","As a relatively small engineering firm, we are large enough to bring serious expertise in backend systems, various architectures, data platforms, mobile, and modern DevOps practices, but small enough to stay personal. We typically engage with clients in a way that combines architecture and org-design guidance with hands-on delivery: we don't just advise, we build alongside their teams and help them internalize these practices.","In practice, that means:","<ul>","<li class='ml-4'>We organize around value streams rather than just technologies. Teams are shaped to own meaningful slices of functionality rather than narrow technical roles.</li>","<li class='ml-4'>We use DDDâstyle thinking and collaborative techniques such as event storming to understand a client's domain, identify subdomains and bounded contexts, and make integration points explicit before we decide on architectures or te
1chnologies.</li>","<li class='ml-4'>We use DORA metrics as a shared language with our clients and internally. When we propose changesânew pipelines, new team boundaries, or refactoring strategiesâwe connect them to measurable improvements in lead time, deployment frequency, reliability, and recovery.</li>","<li class='ml-4'>We look at SPACEâstyle dimensions to understand how it feels to build and operate a system. We pay attention to developer satisfaction, communication friction, and time in flow, not just ticket throughput.</li>","<li class='ml-4'>We invest in a frictionless developer experience both for our own teams and for the teams we partner with: templates, service chassis, CI/CD blueprints, observability patterns, and automation that reduce repeated effort.</li>","<li class='ml-4'>We treat architecture as a maturity journey. For some clients, that means strengthening a modular monolith and clarifying ownership. For others, it means carefully introducing more distributed and eventâdriven components where there is a clear payoff and the organization is ready for the complexity.</li>","</ul>","Because we combine theory with dayâtoâday delivery, our clients don't just get code. They get a healthier way of working: clearer boundaries, faster feedback, and systems that are easier to evolve. And our own engineers get to work in environments where the principles they read about, like fast flow, healthy metrics, frictionless DX, are actively pursued, not just theorized.","<span class='text-2xl font-bold'>Bringing It All Together</span>","In the end, healthy software organizations are not defined by whether they run on microservices, Kubernetes, or any other specific technology. They are defined by how well they enable small, focused teams to own outcomes, evolve their architecture safely over time, and work in an environment where doing the right thing is the path of least resistance.","DORA and SPACE give us a way to see whether this is actually happening. They connect structure, architecture, and human experience into a single, coherent picture. Flow, reliability, and developer happiness stop being abstract aspirations and become measurable, improvable qualities of the system.","At Datawise.ai, this is the lens we use every day, both internally and in our client work. We combine domainâcentric design, pragmatic architecture, and frictionless developer experience to create systems that can keep changing at a steady pace and keep producing predictable outcomes for our clients.","If you are trying to modernize an existing platform, build a new product, or simply give your teams a healthier environment to work in, this way of thinking is not a luxury. It is a real competitive advantage."],image:i.src,imageUrl:"/images/healthy-software.jpg"},{date:"Oct 21, 2025",id:"the-elite-software-engineer",title:"The Elite Software Engineer: Lessons in Managing Complexity",paragraphs:["Every piece of software, no matter how small, hides layers of abstraction, interdependencies, and design choices that can quickly spiral into chaos. The ability to tame that complexity, to make systems understandable, evolvable, and resilient, is what separates good engineers from great ones.","From my experience at Datawise, Iâve learned that great software engineering is about curiosity, putting the effort to evolve and having empathy. Tools evolve, AI assistants improve, and frameworks come and go, but the challenge of building understandable, adaptable systems remains the same, so is the journey of the evolution of a software developer. Our philosophy is grounded in pragmatic innovation and engineering excellence: we approach complexity not as something to eliminate entirely but as something to manage with discipline. Every engineer, regardless of seniority, shares the same mission, to deliver value to the stakeholders and to evolve personally.","<br/>","<b>1. From Syntax to Substance</b>","When we first learn to code, writing working programs feels like the goal. You learn about variables, loops, arrays, and functions and once you make the computer do what you want, you feel like a magician. But thatâs just fluency, not mastery. Itâs like knowing how to spell and form sentences, it doesnât make you a great author.","The real challenge begins when you start to build systems rather than scripts, when the question shifts from âdoes it work?â to âcan it evolve?â","At Datawise, we see this as the first turning point in a developerâs growth. True evolution begins when curiosity replaces certainty, when you start asking why things work the way they do and how your choices will affect others who touch the system after you. We encourage engineers to go beyond syntax and frameworks to understand the deeper intent behind design and architecture.","That shift, from code that works to systems that last and evolve, is the foundation of how developers grow into engineers.","<br/>","<b>2. Design Is Where Engineering Begins</b>","Software rarely works perfectly the first time. Every iteration, every new feature, and every bug fix adds complexity. Unless we manage it, complexity grows faster than our understanding of the system. Thatâs why good design matters so much. Readable, modular, and changeable code is not a luxury, itâs the foundation for sustainable delivery speed and long-term reliability.","At Datawise, we recognize two forms of complexity. Essential complexity arises naturally from the domain and the problems weâre solving. Accidental complexity, on the other hand, comes from the way
1we design, structure, and implement our systems. Our goal is simple, reduce accidental complexity while managing essential complexity within clear, purposeful boundaries across systems, modules, and components.","Architecture, testing strategy, development practices, and team cohesion all play a critical role in creating and maintaining a good design. These elements act as the connective tissue between technical quality and human collaboration. Architecture provides the blueprint that ensures clarity of purpose and scalability; testing strategy transforms assumptions into verified confidence; disciplined development practices keep the delivery rate consistent; and team cohesion turns individual contributions into collective success. Together, they create a feedback loop of learning and improvement, one that prevents complexity from becoming chaos and allows systems to evolve predictably and sustainably.","<br/>","<b>3. Thinking in Systems, Not Files</b>","At some point, every developer realizes that the real skill isnât writing more code, itâs structuring it. Great engineers think in models and abstractions. They focus less on frameworks and syntax, and more on how the system represents the problem itâs solving.","This is where approaches like Domain-Driven Design, the C4 model, and thinking in systems come in. They help us see software as an evolving model of a real-world problem, one we can reason about without holding every detail in our head while being able to effectively communicate it to all stakeholders.","The key, however, is not to overdo it and try to predict any possible future scenario. Abstraction should simplify things, not complicate them. Design for whatâs needed today, and insulate yourself from the unknown, rather than trying to predict it.","At Datawise, we bring this philosophy to life through modular architectures, clear boundaries, and shared understanding fostered by architecture and domain diagrams and design journaling, all with the same end goal: to manage complexity for developers and our customers while continuously adjusting to feedback. These practices help teams be truly Agile and align around a common, evolving vision of the product.","<br/>","<b>4. From Problem Solver to Technical Leader</b>","Truly elite engineers arenât just problem solvers, theyâre problem explorers. Theyâre comfortable starting projects where the outcome isnât fully known. They use prototypes, experiments, and iteration as tools for learning.","At this stage, technical skill blends with something deeper: communication and leadership. Being able to explain complex ideas simply, to junior engineers, to product managers, to clients, is one of the most powerful forms of expertise.","As Richard Feynman said, âIf you canât explain it simply, you donât understand it well enough.â Teaching, mentoring, and articulating your reasoning are not side skills, they are the essence of mastery.","At Datawise, we see this mindset reflected across our teams. Engineers are encouraged to explore, challenge assumptions, and share their insights. Just as importantly, we emphasize empathy for all evolving parties in a software project by trying to understand each person's perspective. Great technical leadership means being able to step into their shoes, anticipate their needs, and communicate in ways that make complex systems accessible. We value those who not only find solutions but help others understand the path that led there, turning individual expertise into collective growth.","<br/>","<b>5. Beyond Code: Context and Continuous Growth</b>","Elite developers understand their systems in context, thinking about the why behind the code: the business needs, user experience, and trade-offs that shape every decision. They know how software is delivered, deployed, observed, and improved over time, and they apply this awareness to every stage of development.","Some specialize deeply like in distributed systems, concurrency, or performance.","Others excel at bridging teams, translating complexity into clarity, and driving engineering culture forward.","The common ground is that developers need to continuously invest in personal and technical growth. Skill evolution is integral to leadership, it ensures we stay relevant and effective as technologies and practices change.","At Datawise, we encourage engineers to learn, share, and teach. We utilize ways to share what we have learned, both from our successes and our mistakes, celebrate innovation, and open discussions to refine our craft. We see every challenge as a learning opportunity and every delivery as a chance to improve how we work together.","<br/>","<b>The Datawise Way</b>","Thereâs no single path to becoming an elite software engineer, but shared values help to fulfill someone's potential. At Datawise, we combine curiosity with discipline, collaboration with ownership, and speed with quality. We believe the best systems, and the best engineers, emerge through thoughtful iteration and open collaboration."],author:"By Manos Tzagkarakis, Lead Engineer at Datawise.ai",image:a.src,imageUrl:"/images/elit.jpg",teaser:"The journey to becoming a great software developer has never been easy, not even in the age of AI assistance. While large language models can autocomplete code or summarize documentation, they canât eliminate the real challenge: learning how to manage complexity."},{id:"bu-intelligence-before-ai",date:"Sept 29, 2022",title:"(BU) intelligence before AI",author:"Datawise.ai",teaser:"From BI and UI all the way to AI. A roadmap for building an AI-first company. How to build solid foundations without blowing up the costs and making the best use of your engineering resources.",paragraphs:["Letâs admit it; there is no company or individual who doesnât suffer from a little bit of FOMO (Fear Of Missing Out) syndrome. So when the world is buzzing with AI and deep learning breakthroughs daily, engineers and executives get anxious and donât want to miss the train. We often get calls from companies asking us to start projects about putting AI initiatives in motion. Caught on buzzwords like GPT-3 and BERT etc., they are asking us how they can get them into their product.","There are many issues with a request âI want our company to do Machine Learning or Artificial Intelligence.â The very first question that any company should ask is, âHow can I make the product better?â. Yes, AI can most likely improve your product, but only if you have the right foundation in place. It is always a good idea to see what the leaders in AI like Google do. If we look at the history of Google, we see that there were tw
1o pillars of its early success before the rise of AI. The first one was its ability to collect data and do business intelligence at scale. The next step was to clean the data at scale in order to either train ML models or populate huge knowledge graphs like Google Maps. There is a misconception that this is done completely automatically with AI. The truth is that AI is used heavily, but human annotators have the last word. The extent of human crowd work is described really work in the book âGhost workâ by Mary Gray. The point is that the human-in-the-loop AI process is made possible by efficient and well-designed User Interfaces that multiply annotators' throughput of generating clean data at scale.","In other cases, UIs are designed so that the users are empowered to provide the desired data without the use of AI at all. A simple question like âWas that helpful?â can be better answered directly versus an AI guess.","At last, donât forget that in order to train an AI model, you need a rather complex pipeline for cleaning data and creating features that are based on BI systems.","If you want to build a roadmap for AI, make sure that you set up your operations properly to optimize UI first, then see how far you can go with BI. Then you are ready to start thinking about implementing AI. We have been part of this journey several times, and we always enjoy it!"],image:t.src,imageUrl:"/images/bit.png"}];e.s(["default",0,o],48086)},16736,e=>{"use strict";e.s(["default",0,[{slug:"citizen-digital-services-platform",title:"Citizen Digital Services Platform",subtitle:"A government-backed platform enabling citizens of Uzbekistan to seamlessly access financial and social services with secure onboarding, compliance, and modern digital experiences.",highlights:[{title:"Problem Statement",description:"Fragmented citizen services across multiple providers, inconsistent onboarding processes, and compliance risks with financial and identity regulations.",icon:"alert-triangle"},{title:"Approach",description:"Delivered a secure, modular, eventâdriven citizen services platform with deep integrations to national systems (Banks, NASP, Visa Flex, MyID, etc.), streamlined onboarding, and a unified ecosystem.",icon:"activity"},{title:"Results",description:"Unified onboarding flow, secure citizen account claim process, integrated banking and payments, scalable infrastructure, and full regulatory compliance (PCIâDSS)",icon:"trending-up"}],domain:"EâGovernment & Financial Services",techStack:["<b>Backend</b>: Java, Spring Boot, Spring Security","<b>Auth & Identity</b>: Keycloak, MyID, biometric face verification APIs","<b>Data</b>: PostgreSQL, MinIO, Redis, MongoDB","<b>Messaging/Eventing</b>: RabbitMQ","<b>DevOps</b>: Kubernetes, Docker, Prometheus + Grafana, HashiCorp Vault, Nginx","<b>Frontend</b>: SPA (Reactâbased), Android and iOS apps built with Flutter","<b>Other</b>: Multilingual support, advanced face verification"],problemStatement:["Citizens faced significant barriers to accessing digital services due to fragmented processes, duplicate data, and the absence of a unified identity and compliance framework. Onboarding was inconsistent, often manual, and lacked strong verification, creating both user friction and regulatory challenges. In addition, the government needed more effective ways to ensure that social benefit funds were spent according to program rules, requiring mechanisms for controlled disbursement and oversight."],solution:["Citizen Digital Services Platform introduced a unified digital citizen services platform: <br />","<b>Citizen Onboarding</b>: Registration via national ID with biometric face recognition.","<b>Identity Claim Flow</b>: Automatic registrations with laterâstage identity confirmation.","<b>Banking Integration</b>: Full range of servicesâcard issuance and operations, peerâtoâpeer payments, and utility bill payments.","<b>Government Services</b>: Application forms and document wallet for secure storage and retrieval.","<b>Unified QR Identification</b>: A single QR identity usable across financial and government touchpoints.","<b>Authentication</b>: OAuth 2.0 with extended Keycloak flows and JWTâbased secure API access.","<b>Notifications & Messaging</b>: Centralized notification API with multiâchannel delivery.","<b>
1Infrastructure</b>: Scalable, redundant, and secure architecture, fully deployed on bareâmetal infrastructure to comply with national regulations."],outcomes:["<b>Citizen Experience</b>: Intuitive mobile and web access to financial and government services with fast, secure onboarding.","<b>Compliance</b>: Full alignment with national regulations, financial standards, and PCIâDSS certification.","<b>Efficiency</b>: Reduced duplication, streamlined workflows, and optimized identity and payment processes. Despite limited cloud tooling and small, varied teams, development was successfully transitioned to local Uzbek engineers for seamless ownership after launch.","<b>Scalability</b>: Proven ability to scale, supporting up to 15 million eligible users while monitoring key performance metrics.","<b>Extensibility</b>: Modular platform ready for rapid expansion to new eâgovernment and financial services."],image:"/images/case-studies/citizen-digital-services-platform.jpg"},{slug:"threat-exposure-management-platform",title:"Threat Exposure Management Platform",subtitle:"A Datawise-delivered cybersecurity platform providing enterprises with comprehensive visibility, prioritization, and mitigation of cyber risks",highlights:[{title:"Problem Statement",description:"Enter prises face constant cyber threats, fragmented security tooling, and limited ability to prioritize exposures based on business impact.",icon:"alert-triangle"},{title:"Approach",description:"Delivered a next-generation Threat Exposure Management platform aligned with global frameworks (MITRE ATT&CK, NIST), designed to consolidate, analyze, and act on risk data.",icon:"activity"},{title:"Results",description:"Improved security and monitoring for enterprises. Enhanced attack surface visibility, contextual risk prioritization, and measurable reduction in cyber exposure across client organizations",icon:"trending-up"}],domain:"Cybersecurity & Threat Exposure Management",techStack:["<b>Backend</b>: Java, Spring Boot","<b>Frontend</b>: React","<b>Database</b>: PostgreSQL","<b>Architecture</b>: Modular monolith with event-driven design, leveraging asynchronous messaging and domain-driven design principles","<b>Deployment Models</b>: Delivered both as SaaS and on-premise, with optional multi-tenant configurations. SaaS deployments were hosted on AWS with elastic scaling, observability pipelines, and infrastructure-as-code provisioning. A key novelty was maintaining a single codebase to support all deployment models, while optimizing resource utilization and enabling fine-grained usage monitoring and cost attribution."],problemStatement:["Enterprises struggle to understand their real exposure across dynamic IT landscapes. Security tools operate in silos, leaving gaps in visibility. Prioritization is often based on raw vulnerability counts instead of actual exploitability or business risk. This leads to wasted remediation efforts and unaddressed critical risks."],solution:["Datawise delivered a unified Threat Exposure Management platform:","<b>Continuous Visibility</b>: Aggregates data across IT, cloud, and security tools.","<b>Risk-Based Prioritization</b>: Scores exposures by exploitability, asset value, and business context.","<b>Exposure Intelligence</b>: Aligns with MITRE ATT&CK to map threats to adversary techniques.","<b>Integrated Workflows</b>: Connects to ticketing and SIEM/SOAR systems for automated response (50+ integrations).","<b>Flexible Deployment</b>: Same codebase delivered as SaaS or on-premise, with optional multi-tenant configurations, giving enterprises choice without added complexity.","<b>Analytics & Reporting</b>: Provides real-time dashboards for CISOs and compliance teams."],outcomes:["<b>Improved Security Posture</b>: Reduced mean time to remediate critical exposures.","<b>Actionable Insights</b>: Clear guidance for IT and security teams to focus on the most impactful issues.","<b>Operational Efficiency</b>: Consolidated multiple tools into one platform, lowering costs and complexity.","<b>Strategic Alignment</b>: Enabled enterprises to align exposure management with business and regulatory requirements.","<b>Deployment Flexibility</b>: SaaS and on-premise models ensured adaptability for customer environments, while a single codebase reduced maintenance overhead and simplified monitoring."],image:"/images/case-studies/threat-exposure-management-platform.jpg"},{slug:"restaurant-hospitality-inventory-cost-management-platform",title:"Restaurant & Hospital
1ity Inventory & Cost Management Platform",subtitle:"A Datawise-delivered SaaS platform enabling restaurants and hospitality groups to manage inventory ordering, recipe costs, supplier relationships, waste, and profitability â while also connecting merchants directly with suppliers through a built-in marketplace.",highlights:[{title:"Problem Statement",description:"Restaurants lacked a unified platform for managing inventory, ordering supplies, and controlling food costs. Manual workflows and disconnected POS systems made it difficult to understand true profitability and optimize procurement.",icon:"alert-triangle"},{title:"Approach",description:"Delivered a domain-driven, event-driven, multi-tenant platform combining inventory management with a supplier marketplace.",icon:"activity"},{title:"Results",description:"Empowered merchants to optimize costs and streamline stock management, while enabling suppliers to directly service restaurants via the platform, fostering transparency and efficiency across the supply chain.",icon:"trending-up"}],domain:"Restaurant & Hospitality Technology",techStack:["<b>Backend</b>: Java, Spring Boot","<b>Architecture</b>: Hexagonal, modular monolith, event-driven, multi-tenant, , Domain-Driven Design (DDD)","<b>Frontend</b>: React (SPA webapp, both merchant and supplier apps). React Native for mobile for cross platform mobile apps.","<b>Data Layer</b>: PostgreSQL for structured data, ElasticSearch for catalog/ingredient/inventory search, and S3-compatible object storage for files and reports","<b>Deployment</b>: Cloud-native on GCP with containerized services","<b>Other</b>: Integration with Spotlight POS and external supplier systems"],problemStatement:["Restaurants and hospitality groups faced challenges managing inventory orders, recipes, supplier relationships, and waste. POS systems tracked sales but lacked insights into food costs, stock levels, or procurement needs. Suppliers had limited visibility into merchant demand, leading to inefficiencies in replenishment and missed opportunities for direct engagement."],solution:["Datawise delivered a unified inventory and supplier marketplace platform:","<b>Inventory Ordering</b>: Automated stock ordering to ensure kitchens and outlets remain supplied.","<b>Supplier Marketplace</b>: Merchants could buy directly from suppliers onboarded on the platform, supported by a dedicated supplier app.","<b>Recipe & Supplier Management</b>: Centralized catalog, recipe costing, and supplier contracts in one platform.","<b>Advanced Reporting</b>: Dashboards covering COGS%, turnover, waste, menu engineering, and profitability analysis.","<b>Search & Accessibility</b>: ElasticSearch-powered free-text search across suppliers, products, recipes, and inventory.","<b>Multi-Tenant Flexibility</b>: Supported two distinct tenant types â merchants and suppliers â within a single codebase.","<b>Integration</b>: Real-time data sync with Spotlight POS for accurate consumption and cost tracking.","<b>Deployment</b>: SaaS and enterprise-ready on GCP, with scalability, resilience, and strong security practices."],outcomes:["<b>Operational Control</b>: Enhanced visibility into stock levels, ordering, and waste across outlets.","<b>Profitability</b>: Improved cost management and menu engineering, reducing waste and increasing margins.","<b>Supplier Empowerment</b>: Gave suppliers a digital channel to connect directly with merchants and fulfill orders.","<b>Speed & Consistency</b>: State-of-the-art development practices (DDD, automated testing, static code analysis, peer reviews) ensured rapid, reliable delivery.","<b>Scalability</b>: Multi-tenant, event-driven architecture supporting both merchant and supplier networks.","<b>Future-Ready</b>: Extensible platform adaptable to new integrations, reporting needs, and supply chain models."],image:"/images/case-studies/restaurant-hospitality-inventory-cost-management-platform.jpg"},{slug:"global-real-estate-company",metaTitle:"From $250M to $2B: AI Revenue Optimization in Real Estate",title:"From $250M to $2B: Driving Transformation with AI-Powered Revenue Optimization for a global real estate company",subtitle:"How our full-house engineering agency partnered with a leading global real estate company to unlock exponential growth by combining data science, machine learning, and commercial strategy.",highlights:[{title:"Location Recommendation Engine",description:"Built a location recommendation engine guiding global expansion into high-yield cities and micro-markets.",icon:"star"},{title:"Workspace Design Optimization",description:"Optimized workspace design through predictive analytics to maximize utilization and member satisfaction.",icon:"chart"},{title:"Enterprise Pivot",description:"Pivoted pricing model from SMB/consumer focus to enterprise clients, which grew to 40% of total revenue.",icon:"trending-up"},{title:"Dynamic Pricing & Discounting",description:"Rolled out dynamic pricing & discounting engine using behavioral signals, contract duration, and demand patterns.",icon:"globe"},{title:"Account Growth Scoring",description:"Designed an account growth scoring model to segment customers, predict demand, and calculate lifetime value.",icon:"users"}],domain:"Real Estate, Shared Workspaces, B2B SaaS Pricing & Revenue Optimization",techStack:["<b>
1Backend</b>: Java, Spring Boot, Spring Security","<b>Auth & Identity</b>: Keycloak, MyID, biometric face verification APIs","<b>Data</b>: PostgreSQL, AWS Redshift, Redis, MongoDB","<b>Messaging/Eventing</b>: SQS, RabbitMQ","<b>DevOps</b>: AWS EC2, Kubernetes, Docker, ","<b>Frontend</b>: ReactJS","<b>Other</b>: SageMaker, Airflow"],problemStatement:["Company was scaling quickly but faced structural challenges:","<b>Expansion Risk</b>: Location selection was often opportunistic, with inconsistent ROI.","<b>Revenue Model Strain</b>: Heavy reliance on freelancers and small businesses created churn and limited stability.","<b>Static Pricing</b>: Flat desk pricing ignored demand signals and contract length.","<b>Customer Blind Spots</b>: No systematic framework to identify expansion-ready accounts or project lifetime value."],solution:["<b>Expansion & Space Optimization</b>: Location Recommendation Engine: ML models on geospatial, demographic, and competitive datasets. Space Optimization: IoT sensor + booking data â predictive models for desk mix (hot desk vs. private office) â design changes tied to demand lift.","<b>Pricing Transformation</b>: Enterprise Pivot: Data dashboards showed enterprise clients had higher lifetime value and lower churn â partnered with GTM team to reframe offering. Dynamic Pricing Engine: Deployed ML models adjusting desk pricing by demand, contract duration, and behavior patterns.","<b>Customer Intelligence & Retention</b>: Account Growth Scoring Model: Tracked funding rounds, hiring signals, and utilization to predict expansion likelihood. CLV Framework: Guided retention strategy and upsell campaigns."],outcomes:["<b>8x Revenue Growth</b>: From $250M to $2B in two years, with ML-driven revenue optimization central to scaling.","<b>Expansion ROI</b>: +30% improvement on new site performance.","<b>Enterprise Success</b>: Enterprise clients contributed 40% of total revenue by 2019.","<b>Yield Optimization</b>: Dynamic pricing added 18% lift in revenue per desk.","<b>Customer Intelligence</b>: CLV analytics drove 25% higher upsell conversions."],image:"/images/case-studies/global-real-estate-company.jpg"},{slug:"luxury-b2b-transformation",title:"Luxury B2B Transformation â Commerce, Sales, Supply Chain, UX & Growth Marketing",subtitle:"How our full-house engineering agency replatformed a heritage luxury brandâdeprecating legacy systems, automating supply chain and sales processes, revamping UI/UX, and launching personalization and growth engines that became the companyâs fastest driver of revenue.",highlights:[{title:"System Migration",description:"Built a new B2B commerce stack while deprecating all legacy systems, migrating workflows without downtime.",icon:"arrow-left-right"},{title:"Scale",description:"Platform serves 20K SKUs, each with multiple sub-products, metadata, and sample variants.",icon:"bar-chart-3"},{title:"ERP Integration",description:"Fully integrated and customized existing ERP, unifying orders, inventory, and finance.",icon:"settings"},{title:"CRM & Sales Enablement",description:"Delivered a mini-CRM for 200+ reps, integrated with Outlook, Zoom, and Slack.",icon:"users"},{title:"UX Revamp",description:"Streamlined flows to minimize clicks to checkout, increased AOV and frequency, and designed UX focused on driving user value and adoption through continuous feedback loops.",icon:"layout-dashboard"},{title:"Supply Chain Optimization",description:"Automated the end-to-end receiving process, reducing warehouse staff by 35% while increasing throughput by 25%.",icon:"truck"},{title:"Personalization & Growth",description:"Built proprietary PLPs and visit-based intelligent email campaigns (not cookie-driven), becoming the fastest-growing revenue engine.",icon:"sparkles"},{title:"Customer Intelligence Dashboards",description:"Delivered real-time segmentation & KPI dashboards across ERP, commerce, and CRM, empowering sales & executives.",icon:"bar-chart-3"},{title:"Returns Automation",description:"Built self-service returns workflow integrated with ERP, reducing turnaround times.",icon:"undo-2"}],domain:"Luxury B2B Commerce, Supply Chain Automation, ERP Integration, UX Transformation, Personalization & Growth Marketing, Real-Time Analytics",techStack:["<b>
1Backend</b>: Java, Spring Boot, Spring Security","<b>Auth & Identity</b>: Keycloak, MyID, biometric face verification APIs","<b>Data</b>: PostgreSQL, AWS S3, Elastic","<b>Messaging/Eventing</b>: Kafka","<b>DevOps</b>: EBS, Lambda, Prometheus + Grafana","<b>Frontend</b>: NextJs, ReactJs"],problemStatement:["The brand faced structural challenges:","<b>Legacy Sprawl</b>: Outdated, siloed systems with rising costs.","<b>Scale Complexity</b>: 20K SKUs, each with multiple sub-products, samples, and fulfillment workflows.","<b>ERP Bottlenecks</b>: GP Dynamics poorly integrated.","<b>UX Friction</b>: Long checkout journeys, low adoption, poor personalization.","<b>Supply Chain Inefficiency</b>: Manual, labor-heavy warehouse operations.","<b>Sales Dependency</b>: Most revenue required rep involvement, limiting scale.","<b>Weak Marketing</b>: Cookie-based campaigns lacked effectiveness.","<b>Data Blind Spots</b>: No unified view of KPIs or customer segments"],solution:["<b>Foundation & ERP Integration</b>: Built a custom commerce stack, deprecated all legacy systems while maintaining continuity, fully integrated existing ERP for orders, inventory, and finance","<b>UX Revamp & User Adoption</b>: Streamlined checkout (fewer clicks, higher AOV, more frequent buying). Built PDP flows with real-time stock, reservations, and guided journeys. Laser-focused on user value.","<b>Supply Chain & Warehouse Optimization</b>: Automated end-to-end receiving. Introduced barcode scanning, event-driven workflows, and real-time dashboards. Achieved +25% throughput with -35% staffing in warehouses. Improved operational controls, accuracy, and cost efficiency.","<b>Personalization & Growth Engine</b>: Custom PLPs: Hyper-personalized product listings tailored to buyer type, behavior, and journey stage. Intelligent Email Campaigns Triggered by real visits (online & offline), not cookies â driving awareness, intention, and conversions. These campaigns became the #1 growth engine of digital revenue. Launched real-time segmentation dashboards across commerce, ERP, and CRM â gave sales teams and executives clarity on funnel health, demand, and customer segments."],outcomes:["Digital Control: All legacy systems sunset, engineering fully transitioned.","<b>Scale Mastery</b>: "," UX Wins"," Checkout simplified â fewer clicks."," Higher average order value."," Higher order frequency."," Stronger user adoption through feedback-driven design.","<b>Supply Chain Efficiency</b>: -35% staff, +25% warehouse throughput.","<b>Revenue Growth</b>: Personalized PLPs and intelligent campaigns became the fastest-growing revenue channel.","<b>EBITDA Impact</b>: Automation + direct digital revenue mix materially boosted margins.","<b>Sales Uplift</b>: CRM adoption increased rep productivity across 200+ users.","<b>Executive Visibility</b>: Real-time dashboards enabled faster, more informed decisions."],image:"/images/case-studies/luxury-b2b-transformation.jpg"},{slug:"teach-your-agents-how-to-use-tools",title:"Teach your agents how to use tools",subtitle:"Train your agents on complex tasks",metaDescription:"We design validated, tool-based training datasets that help frontier LLM companies teach their agents to solve complex, multi-step tasks.",highlights:[{title:"Problem statement",description:"Even frontier LLMs struggle to solve complex tasks that require tools. While the web offers an abundance of information, there are not that many datasets for training agents to solve problems with tools. Designing datasets at scale is not a trivial task",icon:"alert-triangle"},{title:"Approach",description:"We have a unique team of diverse scientists and engineers who uses sophisticated GenAI processes to design datasets for training LLMs to solve difficult problems. Our datasets are 100% validated proven to lift performance",icon:"activity"},{title:"Results",description:"We are providing high end datasets to the Frontier LLM companies. Our training data follow the terminal bench <a class='text-brand-0' href='https://www.tbench.ai' target='_blank'>tbench.ai</a> format and go through rigorous validation and testing. In a batch of 1000 tasks one problematic training point can ruin the results. We guarantee the quality of our data.",icon:"trending-up"}],domain:"LLM Reinforcement Learning training",techStack:["Tbench.ai, OpenAI, Anthropic, Google, LLama, Docker"],problemStatement:["Create tasks that a language model can perform with the use of tools (databases, planners, scientific software, etc)"],solution:["Generate task descriptions and docker files that contain the tools. Provide a grader and a solution to the problem. Validate the difficulty of the problem and prove that the LLM cannot cheat in order to hack the reward function."],outcomes:["High quality datasets and trained models that demonstrate the lift in the performance"],image:"/images/case-studies/teach-your-agents-how-to-use-tools.jpg"},{slug:"build-genai-native-apps-on-snowflake",title:"Build GenAI native apps on Snowflake",subtitle:"Build Knowledge Graphs on your Snowflake database with GenAI",metaDescription:"A native Snowflake app that builds a knowledge graph over structured and unstructured data, enabling GenAI Q&A without data leaving Snowflake.",highlights:[{title:"Problem statement",description:"As companies move all their data in the modern Data Cloud it becomes imperative to build a semantic layer so that they can feed them to GenAI decision tools",icon:"alert-triangle"}
1,{title:"Approach",description:"We built a native app for a Snowlfake tier 1 partner so that their customers can automatically build a Knowledge Graph over their structured and unstructured data and query them.",icon:"activity"},{title:"Results",description:"We built the whole end to end functionality inside Snowflake without moving the data outside of the security perimeter of the database. Our system utilizes Snowflakeâs autoscaling to hundreds of concurrent users",icon:"trending-up"}],domain:"Enterprise GenAI",techStack:["Snowflake","Cortex (AI, Search, Analyst)","Snowflake Intelligence","SPCE Containers","Native App"],problemStatement:["Query your data inside Snowflake (Structured and Unstructured)"],solution:["Build GraphRAG (Knowledge Graph Based Question Answering) inside the Snowflake Security Perimeter with Snowflake Services"],outcomes:["Modernize your Enterprise operations with GenAI without adding more moving parts. Significant ROI"],image:"/images/case-studies/build-genai-native-apps-on-snowflake.jpg"},{slug:"cultural-heritage-data-governance",title:"Data Governance for a World-Leading Cultural Heritage Organization",subtitle:"Î world-leading cultural heritage organization has been turned to Repox to modernize its data infrastructure. Repox provides a flexible, advanced platform to manage, preserve, and share digital collections at scale.",highlights:[{title:"Flexible Data Modelling",description:"Rule based content organization that reflects the organizationâs complex structure. Customizable metadata schemas with multilingual support and 14+ property types, from spatial fields to controlled vocabularies.",icon:"layers"},{title:"Rich Content Support",description:"Unified management of images, audio, video, and 3D models with previews, thumbnails, and optimized versions for reuse.",icon:"images"},{title:"Powerful Search & Discovery",description:"Full-text, faceted, and metadata-based search with saved queries for recurring needs.",icon:"search"},{title:"Secure Access",description:"Fine-grained permissions, access lists, audit logs, and internal-only workflows for robust governance.",icon:"lock"},{title:"Extensible Architecture",description:"Headless, API-first platform enabling seamless integrations and future scalability.",icon:"puzzle"}],domain:"Cultural Heritage, Data Governance, Digital Preservation",techStack:["<b>Backend</b>: Java, Spring Boot, Spring Security","<b>Frontend</b>: React, shadcn/ui with Tailwind v4","<b>Database</b>: PostgreSQL, OpenSearch","<b>Storage Layer</b>: MinIO, AWS S3","<b>Messaging</b>: RabbitMQ","<b>DevOps</b>: Docker","<b>Deployment Model</b>: SaaS and on-premise with multi-tenant support"],problemStatement:["The organization was facing significant challenges in managing and scaling its cultural heritage data ecosystem:","<br/>","<b>Fragmented and Inconsistent Data Landscape</b","Disparate and heterogeneous data and metadata sources","Multiple independently developed databases with no unified schema","Incomplete, inconsistent, and varying-quality metadata","Lack of standard vocabularies and controlled terms","<br/>","<b>Data Preparation and Integration</b>","Extensive effort required for data cleaning and normalization","Complex migration processes alongside ongoing digitization","Difficulty managing metadata enrichment and external system integrations","<br/>","<b>Access, Discovery, and Dissemination</b>","Inefficient search and discovery capabilities","Limited capabilities for web-based content dissemination","Need for full compliance with national aggregator standards","Challenges integrating with public portals and partner systems","<br/>","<b>Technical and Infrastructure Constraints</b>","Rapidly growing data volumes raising scalability concerns","Performance limitations of legacy, on-premise infrastructure"],solution:["To overcome its fragmented data landscape and infrastructure limitations, the organization adopted Repox as its central data management platform. Repox provided a unified, scalable environment to govern cultural heritage data across multiple systems, formats, and audiences.","<br/>","<b>Unified Data Governance & Modeling</b>","Flexible, schema-driven metadata engine supporting multilingual and domain-specific elements.","Customizable vocabularies and controlled terms to ensure consistency and interoperability.","Consolidation of multiple heterogeneous databases into a single, standardized platform.","<br/>","<b>Seamless Data Preparation & Integration</b>","Automated workflows for data cleaning, normalization, and enrichment.","Tools for smooth migration of legacy data while supporting ongoing digitization efforts.","Connectors for external system integrations, ensuring interoperability across the digital cultural heritage ecosystem.","<br/>","<b>Advanced Access, Discovery & Dissemination</b>","Full-text, faceted, and metadata-based search for fast discovery across large collections.","Headless architecture enabling integration with institutional portals, public platforms, and research environments.","Built-in compliance with international metadata standards (EDM, Dublin Core) and long-term preservation requirements.","Automated harvesting and publishing to Greek national (EKT) and European (Europeana) aggregators via OAI-PMH.","<br/>","<b>
1Scalable, Secure Infrastructure</b>","Cloud-ready architecture supporting exponential data growth and high availability.","Granular IAM permissions, access-controlled lists, and detailed audit logs for secure operations.","Configurable workflows for internal curation and external dissemination.","<br/>","Together, these capabilities transformed the institutionâs digital infrastructure into a flexible, interoperable, and future-proof ecosystem, enabling both effective internal governance and broader public access."],outcomes:["<b>Data Unification</b>: Reduced fragmented databases from 4+ independent systems to one centralized Repox instance.","<b>Metadata Quality</b>: Achieved 40%+ improvement in metadata completeness and consistency through normalization and controlled vocabularies.","<b>Search Efficiency</b>: Search and discovery time reduced by up to 60% thanks to advanced search.","<b>Content Coverage</b>: Expanded digital repository to include millions of records across text, images, audio, video, and 3D objects.","<b>Integration Speed</b>: Cut data migration and enrichment workflows by 30-50% using Repoxâs flexible modeling and connectors.","<b>Scalability</b>: Supported a 10x growth in data volume without performance degradation.","<b>Compliance</b>: Achieved 100% compliance with national aggregator standards.","<b>Stronger Governance</b>: Unified governance framework ensured consistent policies, workflows, and permissions across the institution.","<b>Improved Collaboration</b>: Researchers, curators, and IT staff now work on a single platform, reducing silos and duplication of effort.","<b>Enhanced Accessibility</b>: Collections are more discoverable by the public, academics, and external partners through improved search and dissemination tools.","<b>Future-Proof Infrastructure</b>: Cloud-ready and scalable architecture removes on-premise limitations and prepares the organization for long-term digital preservation.","<b>Cultural Impact</b>: Enabled wider public engagement by making rich collections (including multimedia and 3D models) easily accessible online.","<b>Decision-Making Support</b>: Advanced queries and reporting provide insights for curatorial planning, digitization priorities, and resource allocation."],image:"/images/case-studies/cultural-heritage-data-governance.jpg"}]])},87511,e=>{"use strict";var t=e.i(48086),a=e.i(16736);let i={nav:{links:[{label:"What We Do",href:"/what-we-do/services",children:[{label:"AI Transformation",href:"/what-we-do/ai-transformation"},{label:"AI Engineering",href:"/what-we-do/ai-engineering"},{label:"Software Engineering",href:"/what-we-do/software-engineering"}]},{label:"Industries",href:"#"},{label:"Our Work",href:"/case-studies"},{label:"Bits",href:"/bits"},{label:"About Us",href:"#",children:[{label:"Who we are",href:"/company"},{label:"Careers & Culture",href:"/careers"}]}],careers:{label:"Careers",href:"/careers"},contact:{label:"Contact us",href:"/contact"}},hero:{headline:["Your AI","Implementation Partner"],subheadline:"From opportunity to measured ROI in 90 days or less.",primaryCta:{label:"Talk to Us",href:"/contact"},secondaryCta:{label:"See Our Work",href:"/case-studies"}},why:{label:"WHY DATAWISE",headline:"We take your AI vision all the way to value.",headlineHighlight:"value.",body:"We embed with your team, identify where AI creates measurable value, implement it within your systems, and connect every initiative to ROI.",steps:[{label:"AI VISION",accent:!1},{label:"VALUE DEFINED",accent:!1},{label:"IMPLEMENTED & ADOPTED",accent:!1},{label:"MEASURED ROI",accent:!0}]},deliver:{label:"WHAT WE DO",headline:"The engineering behind enterprise AI.",headlineHighlight:"AI.",subtitle:"End-to-end engineering for production AI systems â accelerated by proprietary platforms, built for scale.",capabilities:[{number:"01",title:"AI Applications & Agents",description:"Production AI applications, agents, and workflows built around real business operations and user needs.",href:"/what-we-do/ai-engineering#agentic-automation"},{number:"02",title:"AI Integration & Orchestration",description:"Connect models and agents to your data, APIs, systems, tools, and workflows with secure, reliable orchestration.",href:"/what-we-do/software-engineering#system-integration"},{number:"03",title:"AI Platforms & Accelerators",description:"Proprietary low-code platforms that compress implementation from months to weeks â without compromising flexibility or control.",href:"/what-we-do/ai-engineering#ai-native-products"},{number:"04",title:"Data & Knowledge Engineering",description:"Pipelines, retrieval, knowledge graphs, vector infrastru
1cture, and enterprise context that power high-quality AI.",href:"/what-we-do/software-engineering#data-foundations"},{number:"05",title:"Model Engineering & Optimization",description:"Evaluation, routing, fine-tuning, distillation, performance, and inference-cost optimization for maximum impact.",href:"/what-we-do/ai-engineering"},{number:"06",title:"Production AI Infrastructure",description:"Deployment, observability, security, governance, human review, and enterprise-scale reliability from day one.",href:"/what-we-do/ai-engineering#ai-operations"}],platforms:{label:"POWERED BY DATAWISE PLATFORMS",description:"Proprietary platforms purpose-built to accelerate every implementation.",features:["Low-code orchestration","Evaluation & observability","Enterprise knowledge layer","Governance & guardrails","Reusable components"]}},method:{label:"HOW WE WORK",headline:"Decide. Build. Adopt.",headlineHighlight:"Adopt.",subtitle:"One team with you from the first decision to measurable value.",subtitleHighlights:["with you"],steps:[{number:"01",title:"Decide",summary:"We find where AI will create value.",timeframe:"WEEKS 1â2",items:["Prioritize opportunities","Define outcomes & success metrics","Quantify return & build the roadmap"],milestone:"STARTING TOGETHER",href:"/what-we-do/services#strategize"},{number:"02",title:"Build",summary:"We engineer it into your business.",timeframe:"WEEKS 2â8",items:["Engineer & integrate","Test, evaluate & secure","Deploy to production"],milestone:"BUILDING MOMENTUM",href:"/what-we-do/services#build"},{number:"03",title:"Adopt",summary:"We make it part of how your business works.",timeframe:"BY DAY 90",items:["Operate & measure","Drive adoption & enable your team","Optimize & scale with confidence"],milestone:"DELIVERING LASTING VALUE",href:"/what-we-do/services#operate"}]},engage:{label:"WORK WITH DATAWISE",headline:"Start where you are.",headlineHighlight:"you are.",subtitle:"Whether you have an idea, an active project, or AI already in production, we can meet you there.",subtitleHighlights:["we can meet you there."],models:[{label:"I HAVE",title:"AN IDEA",titleHighlight:"IDEA",description:"Strategy Sprint ⢠2â4 weeks"},{label:"I HAVE",title:"A PROJECT",titleHighlight:"PROJECT",description:"Embedded AI Engineers"},{label:"I NEED",title:"IT DELIVERED",titleHighlight:"IT DELIVERED",description:"End-to-End Implementation"}],cta:{label:"Talk to Us",href:"/contact"}},featuredWork:{label:"FEATURED WORK",headline:"See how clients turn AI into real value.",headlineHighlight:"real value.",subtitle:"Production systems across industries â from strategy through measurable outcomes.",cases:[{slug:"global-real-estate-company",industry:"Global Real Estate",title:"AI-powered revenue optimization from $250M to $2B",overlay:"8x",overlayType:"number"},{slug:"threat-exposure-management-platform",industry:"Cybersecurity",title:"Threat exposure management for enterprise security teams",overlay:"50+",overlayType:"number"},{slug:"luxury-b2b-transformation",industry:"Luxury B2B Commerce",title:"Replatforming a heritage luxury brand for B2B growth",overlay:"20K",overlayType:"number"},{slug:"cultural-heritage-data-governance",industry:"Cultural Heritage",title:"Data governance for a world-leading cultural heritage organization",overlay:"REPOX",overlayType:"badge"},{slug:"citizen-digital-services-platform",industry:"E-Government",title:"Citizen digital services platform for national-scale onboarding",overlay:"15M",overlayType:"number"},{slug:"build-genai-native-apps-on-snowflake",industry:"Enterprise GenAI",title:"GenAI-native apps and knowledge graphs on Snowflake"}].flatMap(e=>{let t=a.default.find(t=>t.slug===e.slug);return t?[{slug:t.slug,industry:e.industry??t.domain,title:e.title??t.title,overlay:e.overlay,overlayType:e.overlayType,image:t.image,imageGradient:"from-accent-blue/20 via-bg-elevated to-surface"}]:[]})},resources:{label:"BITS",headline:"Thinking on AI engineering, architecture, and delivery.",headlineHighlight:"AI engineering",subtitle:"Perspectives from the team building production AI systems every day.",featured:[{id:"the-gap-between-ai-spend-and-ai-results",date:"Jun 6, 2026",title:"The Gap Between AI Spend and AI Results",excerpt:"A pattern repeats in almost every conversation we have had with prospective clients over the last year. They have spent a meaningful amount of money on AI subscriptions, on copilots, on chatbots, on a handful of proofs of concept. Some of these investments came from vision."},{id:"ai-augmented-development-demands-from-your-organisation",date:"Mar 4, 2026",title:"What AI-Augmented Development Demands from Your Organisation",excerpt:"The cost of producing working code has been falling for years, and AI coding tools have accelerated that trend dramatically. We do not yet know where the floor is. A single developer, assisted by AI agent(s), can now produce in hours what once took a team days."},{id:"healthy-software-organizations-flow-metrics-dx",date:"Dec 29, 2025",title:"Helping Build Healthy Software Organizations: Flow, Metrics, and Developer Experience at Datawise.ai",excerpt:"Over the past decade, the softw
1are industry has learned a hard truth: you can have excellent engineers, modern cloud infrastructure, and the latest frameworks, and still struggle to deliver meaningful change quickly."}],footer:"Long-form perspectives on building AI that ships, scales, and proves its value.",viewAll:{label:"View all Bits",href:"/bits"}},finalCta:{label:"LET'S BUILD WHAT'S NEXT",headline:"Ready to turn AI into ROI?",headlineHighlight:"ROI?",subtitle:"Start where you are â whether you need a decision, a build, or a partner to run what you already have. The first conversation costs nothing.",subtitleHighlights:["The first conversation costs nothing."],primaryCta:{label:"Talk to Us",href:"/contact"},secondaryCta:{label:"See case studies",href:"/case-studies"}},footer:{columns:[{title:"OUR SERVICES",links:[{label:"Strategize",href:"/what-we-do/services#strategize"},{label:"Build",href:"/what-we-do/services#build"},{label:"Operate",href:"/what-we-do/services#operate"},{label:"How We Engage",href:"/what-we-do/engage"}],footerLink:{label:"See what we do",href:"/what-we-do/services"}},{title:"WHAT WE DELIVER",links:[{label:"Agentic Automation",href:"/what-we-do/ai-engineering#agentic-automation"},{label:"AI-Native Products",href:"/what-we-do/ai-engineering#ai-native-products"},{label:"AI Operating Layer",href:"/what-we-do/ai-engineering#ai-operating-layer"},{label:"AI Operations",href:"/what-we-do/ai-engineering#ai-operations"},{label:"Legacy Modernization",href:"/what-we-do/software-engineering#legacy-modernization"},{label:"Product Innovation",href:"/what-we-do/software-engineering#product-innovation"},{label:"System Integration",href:"/what-we-do/software-engineering#system-integration"},{label:"Data Foundations",href:"/what-we-do/software-engineering#data-foundations"}],footerLink:{label:"Explore capabilities",href:"/what-we-do/ai-engineering"}},{title:"INDUSTRIES",links:e.i(74120).default.cards.map(e=>({label:e.title,href:e.href})),footerLink:{label:"Talk to us",href:"/contact"}},{title:"BITS",links:[{label:"All Bits",href:"/bits"},...t.default.slice(0,5).map(e=>({label:function(e,t=40){return e.length<=t?e:`${e.slice(0,t-1).trimEnd()}â¦`}(e.title),title:e.title,href:`/bits/${e.id}`}))],footerLink:{label:"View all Bits",href:"/bits"}},{title:"COMPANY",links:[{label:"Who we are",href:"/company"},{label:"Our Work",href:"/case-studies"},{label:"Careers & Culture",href:"/careers"}]}],contact:{title:"GET IN TOUCH",hiring:{label:"We're hiring",href:"/careers"},social:[{label:"LinkedIn",href:"https://www.linkedin.com/company/datawise-ai",icon:"linkedin"}]},legal:{copyright:`\xa9 ${new Date().getFullYear()} Datawise. All rights reserved.`,links:[{label:"Privacy Policy",href:"/privacy"},{label:"Terms of Service",href:"/terms"}]}}};e.s(["default",0,i],87511)},74120,e=>{"use strict";e.s(["default",0,{hero:{label:"Industries",title:"Built for the industries that move the world.",titleHighlight:"move the world.",subtitle:"We combine deep industry expertise with AI and data engineering to solve your most complex challenges â and create what's next.",aside:["Industry challenges.","Measurable outcomes.","A more intelligent tomorrow."]},cards:[{number:"01",title:"Financial Services",description:"From fragmented data to intelligent, compliant and growth-ready operations.",stat:{value:"30â50%",detail:"Faster compliance processes"},href:"/industries/finance"},{number:"02",title:"Insurance",description:"From manual processes to intelligent underwriting and claims.",stat:{value:"30â60%",detail:"Faster claims cycle times"},href:"/industries/insurance"},{number:"03",title:"Manufacturing & Supply Chain",description:"From disconnected systems to a more efficient, resilient and autonomous supply chain.",stat:{value:"20â40%",detail:"Lower operating costs"},href:"/industries/manufacturing"},{number:"04",title:"Retail & Commerce",description:"From siloed data to personalized experiences and higher customer value.",stat:{value:"2â5x",detail:"Increase in campaign ROI"},href:"/industries/retail"},{number:"05",title:"Cybersecurity",description:"From reactive defense to proactive, AI-powered protection.",stat:{value:"50â80%",detail
1:"Faster threat detection & response"},href:"/industries/cybersecurity"},{number:"06",title:"Hospitality",description:"From operational complexity to seamless, elevated guest experiences.",stat:{value:"25â50%",detail:"Higher guest satisfaction"},href:"/industries/hospitality"}],features:[{title:"Industry-led approach",body:"Deep expertise. Real-world complexity."},{title:"Measurable impact",body:"Proven results, at scale."},{title:"Built for what's next",body:"Turn industry challenges into opportunity."}]}])},83188,e=>{e.q("/_next/static/media/ai-dev.1vzxrlapfojok.jpg")},15726,e=>{e.q("/_next/static/media/bit.333wucl5di11t.png")},21214,e=>{e.q("/_next/static/media/elit.00hpkfecs2duc.jpg")},91576,e=>{e.q("/_next/static/media/gap.0sv-gqqyax_8-.png")},95935,e=>{e.q("/_next/static/media/healthy-software.1e08fljei08r1.jpg")}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.