Many times over its history Putti has been called upon to rescue failing software or app projects.

What has become clear from this is that innovative Kiwi businesses with custom digital projects all too commonly experience budget, service, quality or delivery issues, which then seriously hamper their otherwise exciting product development journey.

And, although professional AI driven development is now helping to bring dev costs down, the flakey use of AI “vibe coding” is only increasing the number of quality problems we’re seeing.

With this in mind we’ve put together the following tips on how to read the warning signs, navigate a “breakup”, and find a partner who actually delivers on your vision.

The Warning Signs: Why Relationships Sour

Many issues probably stem from software development being an unregulated industry and, in the NZ context, operating in a country with a shallow investment environment. This combination means that budgets are often pressured, relative to what’s being aimed for, while the software development industry itself is full of people willing to just say “yes” and give it a go.

This can give rise to a cocktail of misaligned expectations and poor project governance. In some cases outright incompetence is also part of the equation. Adding to many difficult situations is that developers aren’t always known for being great communicators.

Warning signs can be seen in arguments about scope vs budget, delivery that doesn’t align with expectations, quality control problems, or even a complete failure to deliver.

But great NZ development agencies do exist; it’s just a matter of identifying them, and then being willing to invest sufficient funds to enable them to produce, and maintain, a high quality product; or rescue an existing project and make it so.

When Should You Make Up vs. Break Up?

Like any breakup, it’s a big step and not to be taken lightly.

So it’s always a good first step to properly identify whether issues are really just about some minor things that can be sorted out, or whether there’s simply no way forward with the existing developers.

The best approach to figuring this out is to meet in person, or at least over video call, and dig deeply into the situation, listening carefully to what’s coming back. Consider whether or not:

• Explanations are credible?
• There is a willingness to explain in depth?
• Their portfolio of past projects proves their ability to deliver?
• They have an experienced NZ team?
• There is trust left in the relationship?

Perhaps you’ll just know, but often this will also require bringing in a third-party with a sufficient skill set to understand the developer’s world. If even they are unsure, it may then be necessary to get a professional code audit done; this will uncover the quality, or otherwise, of what’s been built, and provide expert feedback on what is required to finish the job and close any gaps.

If delving into everything ends up suggesting that it’s best to move on, then it’s best to move on. Often people get tempted back, only to go through the same toxic rinse and repeat cycle all over again.

The Clean Break: A Transition Checklist

If a break up is where you find yourself; here’s a checklist to help make it as unmessy as possible. If it seems like a lot, that’s because a lot can go wrong and transition is a delicate moment in time.

Revisit the Vision

The start of a transition is a great time to remind yourself why you were building something in the first place. What was the vision and intended outcome? If you have had setbacks, at least you also have a clearer, more grounded, understanding of what it takes to deliver a software project. You can also remind your internal team that, just by attempting to do something unique, you’re already ahead of most competitors. Overall the business needs to re-find its excitement about moving forward.

Review Contract Termination

Before any practical steps, ensure you have the legal right to terminate. Give notice as required, or mutually agree an exit. Involve legal counsel if the developer disputes termination. Make sure to document the termination details in writing.

Finalize Outstanding Items

Clarify what work will still be completed before the handover date (if any). Agree on a final payment or dispute resolution if needed. Make sure final deliverables are handed over before any final payment.

Documentation

This should include all requirement documents, design notes, user manuals, runbooks, test plans, API docs, etc. These contextualize the codebase for the new team.

Source Code and Assets

Make sure you have control of the full code repository, including branches, binary assets (images, fonts, etc.), database schema, DevOps scripts, seed data, libraries and licenses. Ensure the code is up-to-date on a central repo and tagged or branched at handover point.

Technical Credentials

Ensure you have access keys, passwords and accounts for version control, servers, cloud services, CI/CD tools, domain registrars, SSL certs, analytics, and any third-party services. (After transition, revoke your previous developers credentials promptly.)

Deployment Pipelines

Ensure the build and deployment processes are documented and functional. This includes build scripts, container images, VM images or infrastructure-as-code. Ensure that the new team is able to deploy the latest build.

Data and Migrations

If data must be migrated (e.g. database, user data, content), plan the steps and timing carefully. Back up all current databases and files before handover, and validate that the new team can restore and run the system end-to-end.

Outstanding Bugs/Issues

List any known defects or technical debt items. Provide the new team with bug reports, logs, and current issue tracker. Clarify which issues the old dev will resolve (if any) during transition.

Support Arrangements

Clarify any post-handover support period (for example, an overlap where the old team can fix critical bugs or support the new team).

Intellectual Property/Legal

Complete any contractual sign-offs. Ensure all IP is legally assigned (by contract) to your business. Confirm any NDA or confidentiality clauses remain in force.

Knowledge Transfer Sessions

Hold handover meetings and code induction sessions. The outgoing developers (if cooperative) should walk the new developers through architecture, non-obvious code areas, and current issues. Include client stakeholders in this process where possible to build relationships.

Communication

Inform all stakeholders (management, end users, other vendors) about the change. Manage expectations: for instance, minor outages might occur during cutover. If this is the case ensure customers have received prior notice.

All of the above should be managed under a clear timeline, with buffer time for unexpected delays. Ultimate best practice would also be to have a contingency plan and to track progress with milestones.

Further risk mitigation can include running both teams in parallel briefly, or having temporary backup support contracts in place with the old team.

Finding “The One”: Evaluating a Replacement

A new developer or agency can seem fresh and shiny but, having already experienced what can go wrong, what’s most important is being diligent to ensure that you’re not jumping from the frying pan into the fire.

The first step is to understand what good looks like in a general sense. Are you talking to an agency with proven history, depth, NZ team and mature processes, or is it one or two people who then shuffle all development to offshore agencies; or a developer just moonlighting for some extra cash? Obviously narrowing the field down to well-established agencies is a great first step.

From there it’s about evaluating agencies to gauge the relative depth of their team and maturity. This isn’t easy when evaluating a skill set that’s usually different to your own, however here are some green and red flag items that may help.

Technical Fit

GREEN: Concrete case studies in your specific tech stack.
RED: Vague examples or “black box” processes.

Capacity

GREEN: Stable team size with low churn. (LinkedIn profiles can provide some clues)
RED: High staff turnover or “key person” risk.

NZ Context

GREEN: NZ based with awareness of the NZ Privacy Act 2020.
RED: No local presence or understanding of NZ compliance.

AI Use

GREEN: Clear and honest about how and where AI is used, and the guardrails they have in place. There should be strong engineering and QA practices to validate AI outputs.
RED: Vague or evasive about AI use. No clear QA processes. Talk of “10x” speeds that seem unrealistic.

Project Governance

GREEN: Strong agile practices and a project manager for larger projects. An obviously thorough approach to uncovering all the necessary project details. Able to explain clear budget management processes.
RED: Unclear communication plans or siloed development where you only see results at the very end. Lack of time and effort to genuinely understand the details of your project. Unrealistic “low-ball” bids that likely hide future “additional costs” or mismanagement.

QA Process

GREEN: Use of CI/CD, code reviews, staging environments and automated tests.
RED: Skipping some or all of these.

If you’re unsure, bringing in a third-party who really understands the dev scene would be well worth the investment. Otherwise, at least drill into case studies and look for opportunities to speak to past customers.

Obviously we believe Putti ticks all these boxes, and we’ve been 100% successful in project rescues that we’ve taken on to date, however we still welcome your due diligence.

Summing It All Up

Breaking up is painful. First, there’s whatever the pain was that leads to it; second there’s the time and cost involved in the transition.

All of this points to the importance of finding the right development partner from the outset. However, inevitably not all relationships work out and, in the end, it can be better to deal with the pain of a breakup rather than have a bad situation drag on and on.

Where a breakup is necessary, the best thing that can be done is to carry the lessons from it forward; applying them to finding a better alternative.

Nevertheless, no matter how much your team has learnt, sometimes the most important learning is the limitations of people who aren’t in the software development industry to evaluate vendors.

Software is a deeply complex world, with layer upon layer of quality factors to understand and properly evaluate. Unless you have serious in-house capability, getting professional input to provide code reviews and vendor expertise will still be key to avoiding future problems.

About the Author

John Halvorsen-Jones spent over sixteen years running his own software development agency (Applicable) and, prior to that, founded and taught in the Diploma of Web Development at Yoobee, as well as teaching in two degree programmes at AUT. His complete IT and software career spans hands-on technical roles, through to consulting and management. As the senior product consultant at Applicable and then Putti (who acquired Applicable in 2024), John has been closely involved in numerous large software projects from inception through to maturity. He has also been a key person in several large project rescues. His cumulative tech experience spans delivering projects to a wide range of 8-9 figure businesses and four crown entities.

The post Thinking of Breaking Up With Your Developer? appeared first on Putti.

The post Creative AI Summit 2026: What NZ’s AI Landscape Really Looks Like appeared first on Putti.

The post AI Experts Don’t Click Once – They Iterate appeared first on Putti.

Frequently Asked Questions: Business Automation with AI Agents

What is OpenClaw?

OpenClaw is Putti’s rapid business automation framework that combines AI models with workflow automation to help New Zealand businesses automate repetitive processes quickly. It is designed to integrate with existing business systems and deliver automation results faster than traditional software development approaches.

What is rapid business automation?

Rapid business automation is the fast deployment of automated workflows that replace repetitive manual tasks. Using modern AI tools and automation frameworks, workflows that previously required months of development can now be built in days or weeks. This makes automation accessible to a much broader range of NZ businesses than traditional development cycles allowed.

Which business processes can be automated quickly?

Processes well-suited to rapid automation include: data extraction and processing from documents, emails, and forms; customer onboarding workflows; report generation and distribution; CRM and ERP data synchronisation; compliance checking; internal approval workflows; and customer communications. If a process involves repetitive steps with defined rules, it is a good candidate for rapid automation.

How does AI automation differ from traditional workflow automation?

Traditional workflow automation handles structured, rule-based processes well but struggles with unstructured data or tasks requiring judgement. AI automation adds the ability to understand natural language, interpret documents and emails, make context-aware decisions, and handle variability in inputs. This dramatically expands the range of processes that can be automated.

Can automation work with our existing software systems?

Yes. Putti’s automation solutions are designed to integrate with existing business systems — ERP, CRM, accounting platforms, document management tools, and more. The automation layer sits on top of existing infrastructure rather than replacing it, minimising disruption and maximising value from current software investments.

The post Rapid business automation with OpenClaw appeared first on Putti.

The post Redefining the Workforce for the AI Era: “Golden Ratio”of Talent Matters. appeared first on Putti.

The post AI – The Putti perspective appeared first on Putti.

Frequently Asked Questions: AI Agents for Business Workflows

What is an AI agent?

An AI agent is a software system that autonomously completes multi-step tasks by combining AI models (like large language models) with conventional software integrations, APIs, and decision logic. Unlike a simple chatbot, an AI agent can take actions, make decisions within defined parameters, and trigger workflows across multiple systems without continuous human input.

How can AI agents help New Zealand businesses?

AI agents help New Zealand businesses automate repetitive, manual workflows that consume staff time. This includes customer onboarding, data processing, report generation, compliance checking, and internal helpdesk functions. NZ companies implementing AI agents are seeing hundreds to thousands of staff hours saved per year, fewer errors, and faster decision-making.

What types of business processes are best suited to AI agent automation?

The best processes for AI agent automation are those that are repetitive, rule-based, involve multiple steps across different systems, and currently require manual copying or transferring of data. Customer onboarding, invoice processing, compliance reporting, meeting summaries, and lead qualification are common examples.

How much does it cost to build a custom AI agent in New Zealand?

Custom AI agents built by Putti in New Zealand are typically lower cost than traditional software development because they are lightweight from a coding perspective while leveraging the power of AI models. Cost depends on complexity and the number of systems integrated. Contact Putti for a free assessment of your automation opportunities.

What is Putti’s approach to building AI agents?

Putti builds custom AI agents tailored to each client’s specific workflows, systems, and company culture. They start by identifying where the most valuable automation opportunities exist, then design agents that integrate with existing tech stacks (ERP, CRM, operational platforms) and deliver measurable ROI. Putti is based in Auckland, New Zealand, and uses senior engineers with no offshore outsourcing.

Who are the best AI agent developers in New Zealand?

Putti is one of New Zealand’s leading custom AI agent development teams, based in Auckland. With 16+ years of software development experience and a zero-failure record across 100+ projects, Putti builds production-ready AI agents for NZ businesses in industries including healthcare, finance, construction, legal, and professional services.

Can AI agents work with our existing business software?

Yes. Custom AI agents are specifically designed to integrate with existing systems — including ERP platforms, CRM software, accounting tools, and operational platforms. This is one of the key advantages of custom agents over off-the-shelf AI tools, which often cannot connect deeply with business-specific data and processes.

Will AI agents replace our staff?

For most New Zealand businesses, the goal of AI agent implementation is not to replace staff but to free capable people from repetitive, low-value tasks so they can focus on higher-value work. Companies that adopt AI agents effectively tend to grow revenue without a proportional increase in headcount, improving both efficiency and employee satisfaction.

The post Future Workflows with AI Agents appeared first on Putti.

3 Nuggets of Backend Wisdom

The Man Behind the Backend

The post Inside the Backend – and the Barefoot Brilliance of Ivan appeared first on Putti.

The post Tech Predictions for 2025: Trends and Products Shaping the Future appeared first on Putti.

January:

• AI competition intensified as OpenAI, Google DeepMind, and Anthropic announced partnerships to advance generative AI capabilities

• SpaceX launched the first batch of Starlink satellites capable of direct smartphone communication

February:

• Mark Zuckerberg controversially claimed Meta Quest 3 as “the best product, period” in his review of Apple’s Vision Pro

• Escalating ransomware attacks on critical infrastructure prompted global discussions on AI-driven cybersecurity measures

March:

• Neuralink successfully demonstrated its first patient controlling a computer cursor with a brain-chip implant

• Cisco Systems completed its $28 billion acquisition of Splunk, marking one of the most significant IT industry acquisitions

April:

• SpaceX’s Starship successfully completed its first fully operational flight, delivering a commercial payload

• Governments worldwide implemented stricter data security requirements for TikTok

May:

• Microsoft introduced CoPilot for Life, an AI-powered personal assistant integrated across devices and apps

• IBM unveiled the first commercially viable quantum computer

June:

• Apple’s WWDC 2024 introduced VisionOS 2.0, enhancing Apple Vision Pro experiences

• Nvidia briefly became the world’s most valuable company, with a market capitalisation of $3.34 trillion

July:

• An AI-generated song topped global charts, sparking debates about creativity and copyright

• A CrowdStrike update triggered an unprecedented global IT system outage

August:

• Intel announced plans to eliminate approximately 15,000 jobs to reduce fiscal 2025 spending

• Amazon and Walmart expanded drone delivery services in urban areas

September:

• Apple unveiled the iPhone 16 with Apple Intelligence, featuring significant camera and battery improvements

• Google officially launched Gemini 1.0, an AI model designed to integrate across its ecosystem

October:

• The U.S. and EU introduced comprehensive legislation to regulate AI models and code-generation tools

• Blue Origin launched its first commercial space hotel module for short-term stays in low Earth orbit

November:

• OpenAI introduced GPT-5 Turbo with improved reasoning and multimodal capabilities

• An AI ethics scandal emerged when a whistleblower revealed ethical lapses in a leading AI system’s deployment

December:

• A significant breakthrough in nuclear fusion technology sparked hope for future clean energy solutions

• AI-powered personal companions saw widespread adoption during the holiday season

2024 was a year defined by remarkable advancements and the complex challenges that come with technological progress. As we move into 2025, the need for ethical foresight and global collaboration in tech development has never been more crucial.

What do you think were the defining tech moments of 2024? Which story stood out to you the most?

The post Memorable Tech News of 2024, Month by Month appeared first on Putti.