Building a new AI product while running an established business, with lessons in leadership, focus, and balancing innovation with client commitments.
Launching an AI platform like NRYZE with an experienced team is a different journey from the typical startup path.
At DigiTech Consult, we had an advantage that many startups don’t have from day one. We had an established business, a team with years of experience, and almost a decade of delivering AI and automation solutions to clients across different industries.
Eight developers, two salespeople, three business analysts, a marketing manager, and myself as Founder have all contributed to a shared vision of building something new.
Having an experienced team and an established business gave us a strong starting point, but it also meant balancing product development with existing commercial and client responsibilities.
From Delivering Client Solutions to Building Our Own Product
One of the biggest differences we discovered was that developing a product is not the same as delivering a solution for a client.
For years, we’ve been helping businesses identify opportunities for AI and automation, turning business requirements into working solutions.
We know how to manage complex projects, integrations, demanding requirements, and deadlines.
But when building NRYZE, we suddenly became our own client.
There was no external customer providing a requirements document or approving the scope. We had to challenge our own assumptions, decide which features really mattered, and resist the temptation to build everything we knew was technically possible.
When you have a team capable of building almost anything, saying “not now” can be harder than saying “yes.”
We also had to think differently about commercial success. A client project is successful when it delivers the agreed value. A product is successful when customers repeatedly choose to use it and are willing to pay for it.
The Advantage of Experience and Its Hidden Challenges
Startups with just a handful of co-founders often face steep learning curves, limited resources, and smaller professional networks. Their ability to move quickly is a real strength, but they may need more time to build technical capabilities, establish processes, or understand the market.
Our experience in AI, business analysis, automation, and customer-facing projects gave us a strong foundation. We already understood many of the challenges businesses face, particularly when it comes to managing information across systems, reducing manual work, and improving operational decisions.
This experience also influenced how we approached NRYZE. We were building on challenges we had observed in real business environments rather than starting with a technology and searching for a problem.
When you have specialists from different areas contributing ideas, everyone sees opportunities to make the product better. Developers think about technical possibilities, business analysts about functionality and processes, and salespeople about commercial priorities, potential use cases, and customer expectations.
All perspectives are valuable, but they don’t always lead to the same priorities.
We learned that having more expertise in the room doesn’t automatically mean faster decisions. Sometimes, it means more discussions, more alternatives, and more difficult choices.
Strong product ownership and clear decision-making became just as important as technical capabilities.
The Real Challenge - Innovation Doesn't Stop Client Commitments
Perhaps the biggest challenge was balancing NRYZE’s development with our ongoing client projects.
Unlike a startup where the entire team is focused on one product, DigiTech Consult has existing customers, contractual commitments, support responsibilities, and new business opportunities.
Every hour invested in developing NRYZE is an hour that could potentially be allocated to a paying client project.
This makes resource allocation more than a project management exercise. It’s a business decision.
We approached this by separating dedicated product development time from client delivery hours, supported by clear milestones, regular communication, and shared priorities. We also had to remain flexible because unexpected client requirements or technical issues don’t always follow our plans.
I also learned that protecting time for innovation requires discipline. If a new product is always treated as something the team works on when there is spare capacity, progress becomes unpredictable.
Innovation needs commitment, not just enthusiasm.
Being Your Own Investor Changes the Way You Think
When you’re building a product using the resources of an established business, you become very conscious of the investment you’re making.
It’s not only about development costs, infrastructure, or AI consumption. It’s also about opportunity cost.
Should we invest more time in improving a feature? Is this functionality essential for the first release? Would customers actually pay more for it? Are we solving a real business problem, or are we simply excited about what technology can do?
These are questions we have had to ask ourselves repeatedly.
One of the most difficult things for a technically capable team is accepting that the best product is not necessarily the one with the most features.
We had to learn to distinguish between what is possible, what is useful to customers, and what customers are willing to pay for.
What Almost a Decade of AI Experience Really Gives You
I believe one of our biggest advantages is having experience with what happens after AI solutions are implemented.
Over the years, we’ve worked with businesses across different industries, observed how people adopt new technologies, and experienced the challenges of integrating automation into existing operations.
We’ve also learned that technology alone rarely solves a business problem.
A technically advanced solution may see limited adoption if it doesn’t fit the way people work, adds unnecessary steps instead of making a process more efficient, provides unclear value, or fails to gain enough user trust to become part of their daily routine.
Our ambition is to develop a Sales Decision Intelligence product that helps businesses make better sales decisions, understand their customers, and identify the next steps in an active sales opportunity.
The challenge is translating that vision into a product that is simple enough to use, valuable enough to pay for, and scalable beyond the individual customer projects we’re accustomed to delivering.
And that’s where our next learning curve begins.
Building a Company and Building a Product Require Different Mindsets
Having spent almost a decade building DigiTech Consult, I initially thought developing our own AI platform would be a relatively familiar journey.
What I underestimated was how different the decision-making process becomes when you’re responsible for delivering the solution, defining the problem, validating the market, setting the commercial direction, and deciding where to invest.
As a founder, you also need to learn when to get involved and when to let the team make decisions.
It’s tempting to participate in every discussion, especially when you’re personally invested in the product’s vision. But that can quickly turn you into a bottleneck.
I’ve found that defining the direction, setting priorities, and trusting people to execute are much more valuable than trying to control every detail.
Experience doesn’t eliminate uncertainty, but it helps you make more informed decisions when the outcome is still unclear.
Lessons Learned So Far
We’re still on this journey, and I’m sure there are many more lessons ahead. But a few things have already become clear to me.
Focus is more important than the number of resources. A larger team doesn’t guarantee faster progress if priorities are constantly changing.
Clear ownership matters. When everyone contributes ideas, someone still needs to make the final decision and take responsibility for the direction.
Not every good idea belongs in the first version. Knowing what not to build is just as important as knowing what to build.
Client commitments and innovation must coexist. Both require dedicated time and clear priorities to avoid constantly disrupting each other.
Commercial thinking needs to start early. A technically strong product must also solve a problem that customers consider valuable.
Flexibility is essential. Technical challenges, market feedback, and unexpected business demands will inevitably change your plans.
The Journey Is Just Beginning
Building NRYZE has reminded me of something I learned while growing DigiTech Consult. Creating something new is rarely as straightforward as it looks in the original plan.
I wouldn’t say that developing a product within an established company is easier or harder than starting a business from scratch. The challenges are different, particularly when the same organization has to protect existing client commitments while investing in a product with an uncertain commercial outcome.
For me, NRYZE is also an opportunity to apply what we’ve learned from years of delivering AI and automation solutions to developing a product of our own.
We’re still learning how to balance those responsibilities, make better product decisions, and respond to what customers actually need.
The measure of success will be whether NRYZE becomes a product that sales teams find valuable enough to use regularly and continue paying for.
