Building a new product and developing an existing one
Both scenarios require product understanding and engineering expertise, but they begin with different questions.
Starting with an idea
For a new product, the first challenge is defining what the initial release needs to accomplish. Who will use it? Which problem should it solve first? What information, integrations, and operational tools are necessary for that experience to work?
Discovery and design help turn those questions into a development direction. Decisions about user journeys, architecture, and scope are connected: a seemingly simple feature may depend on an external service, a new data model, or an additional operational workflow.
Our work with MedPal covered this early stage as well as implementation. We helped shape the product through discovery, designed its user experience, built its architecture, and delivered web, mobile, and AI functionality.
Starting with a live product
An existing product brings a different set of constraints: active users, established systems, existing data, and commitments to customers. The starting point is understanding what needs to change and how that change fits into the current product. A new integration may affect authentication, billing, and support. Expansion into another market may require changes to infrastructure as well as the interface.
Our work with LYMA continued beyond the initial mobile application. As the product developed, we added capabilities and supported US expansion through infrastructure designed to handle different regions. The scope of custom development can therefore grow with the product, from an initial release to the systems needed for its next stage.
What Newsoft can take responsibility for
Our custom software development work can cover several connected parts of a product:
| Area |
What the work can include |
| Product discovery |
Understanding user needs, clarifying product goals, and shaping the development roadmap |
| UX/UI design |
User journeys, interface design, and reusable design systems |
| Web and mobile development |
Customer applications, web interfaces, and supporting administration tools |
| Backend engineering |
Product logic, APIs, data structures, and connections between services |
| Integrations |
Connecting payments, commerce platforms, wearable data, and other external services |
| AI capabilities |
Implementing product features such as contextual assistants and personalized insights |
| Quality assurance and further development |
Testing functionality, improving existing flows, and developing subsequent releases |
The combination depends on your starting point. A product with an established design and architecture needs a different engagement from an idea that still requires discovery.
AI is also a scope decision. Some products need it as a core capability; others need reliable workflows, integrations, and a clear interface. In MedPal, AI supports contextual wellness interactions. In LYMA, a third-party analysis capability forms part of a broader customer experience.
How collaboration starts and moves into delivery
Our collaboration workflow begins with an introductory meeting, followed by requirements analysis and an outline of the work, team assembly, project kickoff, and ongoing support.
1. Understand the business need
The first conversation establishes what you are building, where the product stands, and what you want to achieve next.
For a founder, this might be a first release that allows customers to use a new service. For a product leader, it might be a specific roadmap initiative. For a CTO, it might be an integration or architectural constraint that is preventing further development.
This context helps determine where Newsoft can contribute and which experience is relevant to the discussion.
2. Clarify requirements and the initial scope
The next step is translating the business need into an outline of the work.
Depending on the product’s maturity, this may require discovery, design exploration, or a closer examination of existing systems. The questions to resolve include the essential user journeys, integration dependencies, technical constraints, and priorities for the first stage.
MedPal illustrates a broad engagement beginning with discovery. LYMA also began with a discovery phase that covered goals, competitor insights, design direction, technical decisions, and an MVP roadmap. These are examples of how discovery supported those products; its scope will differ for another project.
3. Assemble the team and begin delivery
The team follows the requirements. A mobile application with a backend, external integrations, and a new interface requires a different mix of expertise from a focused extension to an existing web platform.
At kickoff, responsibilities and the working arrangement need to be clear: who makes product decisions, who provides access to existing systems, how feedback is collected, and how progress is reviewed.
4. Develop the product beyond its first release
A first release creates a basis for further decisions. Customer feedback, product usage, and business priorities can reveal what needs to improve or expand.
Our case studies show several forms of continued development: a second iteration and marketplace functionality for Bazo, deeper personalization for LYMA, and analytics capabilities for MedPal.
The scope of ongoing work should reflect the product’s needs and the agreed engagement.
.jpg)
.jpg)
.jpg)
.jpg)
