# External Product Team or In House Hires: How Startups Should Decide

When a startup should bring in an external product team for design, development and AI, when to hire in house, and examples from Pannon Turfgrass and WeChange.

When an external product team beats hiring in house, and what it looks like in practice for Pannon Turfgrass, WeChange, IBC and GlassView.

![IBC IdeaBuilder flowchart canvas, designed and developed by Designatives](https://ipu7rtrtpzxvlstg.public.blob.vercel-storage.com/product-team-thumbnail-ideabuilder.webp)

Tags: Development, UI/UX, SaaS

Sooner or later every startup has more product to build than people to build it. The question is whether to hire designers and engineers in house or bring in an external product team. Both can work. The right answer depends on how soon you need to ship, which skills you need and for how long, and who will own the product a year from now.

We work as an external team for startups and growing companies, covering [product development](https://www.designatives.com/our-services/product-development) from design to code: product design, frontend, mobile, backend, APIs and AI features, together with the brand and the website around the product. This is how we would think about the decision, and what the work looks like in practice.

## When an external product team makes sense

**You need a first version before you can hire.** Recruiting a senior designer and two engineers can take months, and early hires work best when there is a product to hire around. An external team can ship the MVP, usually in eight to twelve weeks, while you recruit.

**You need skills you would only use part of the time.** A product needs UX research, interface design, mobile, backend, integrations and, more and more often, AI. Few startups need all of them full time. An external team brings each one in when the roadmap calls for it.

**There is a date.** A launch, a raise, an event or a promise to a customer. A team that already works together can start shipping in the first weeks.

**Someone else built it and has moved on.** Taking over a product from a previous agency or a team that has left starts with a code review, then fixing what slows you down while new features keep shipping.

## When to hire in house

If the product is the company and the work is steady enough for several full time roles, build your own team, starting with a technical lead who owns the architecture. A good external team makes that easier: it works in your repository from day one, documents as it goes and hands over cleanly when your hires are ready. Many companies do both, with an in house lead and an external team for design, mobile or AI.

## What a full product team should cover

An external team only saves time if it covers the whole job. Ours covers:

**Product design:** research, UX, interfaces and a design system, so new features look and work like the rest of the product.

**Web and mobile:** Next.js, React and TypeScript on the web, React Native or native code for iOS and Android.

**Backend and data:** APIs on NestJS or Laravel, PostgreSQL, and integrations with payments, CRMs and ERPs.

**AI features:** agents, assistants and MCP connectors built into the product and connected to your real systems.

**Brand and website:** the identity, the marketing site, launch films and decks around the product, from the same team, so the product and the company look like one thing.

## What it looks like in practice

Four projects show the range, from a full internal system to product design for a fintech that kept growing.

### Pannon Turfgrass: from brand to the systems that run the business

Pannon Turfgrass is Hungary's largest turf producer. After a rebrand and a new website, we designed and built a [custom ERP system](https://www.designatives.com/our-work/pannon-turfgrass) for order management, logistics and production planning, an iPhone app that gives teams on site real time order data, and a B2B online ordering system for their customers. We have since added an [AI agent](https://www.designatives.com/blog/ai-workflow-optimisation-pannon-turfgrass) inside the ERP that creates invoices, changes orders and updates statuses, and we keep developing the system as the business grows. In the words of their managing director, "our clients especially love the B2B online ordering system."

![Pannon Turfgrass iPhone app designed and built by Designatives, showing real time order data for teams on site](https://ipu7rtrtpzxvlstg.public.blob.vercel-storage.com/product-team-pannon-turfgrass-app.webp)

### WeChange: product design for a fintech that kept growing

[WeChange](https://www.designatives.com/our-work/wechange) lets people change between crypto and cash in more than 190 countries. We designed the brand for launch and kept designing as the company grew: the website and client dashboard, onboarding, buying and selling with local payment methods, the mobile app on the same design system, the WeChange Visa card with its 3D launch film, and everything for TOKEN2049 in Singapore. The result is one product experience on desktop and on a phone.

![WeChange brand system across the mobile app, website, event banner, badge, gift bags and T shirt, designed by Designatives](https://ipu7rtrtpzxvlstg.public.blob.vercel-storage.com/product-team-wechange.webp)

### IBC: a product tool built for a global ideathon

For the [IBC Ideathon](https://www.designatives.com/our-work/ideathon) we created the identity, designed and developed the event website and built the IdeaBuilder, a no code flowchart tool for cross chain ideas. Participants drag in ready made components for token transfers, NFT transfers, queries and control accounts, so they can map how their idea would work on the IBC protocol before they build it.

![IBC IdeaBuilder, a no code flowchart tool for cross chain ideas, designed and developed by Designatives](https://ipu7rtrtpzxvlstg.public.blob.vercel-storage.com/product-team-ibc-ideabuilder.webp)

### GlassView: a long running design partner

[GlassView](https://www.designatives.com/our-work/glassview) is a global video advertising platform. We have redesigned its brand three times, designed its website and made the brand film for Glassview Origin, its neuromarketing product, alongside ongoing consumer design work. As their CEO puts it, "they have been a driving force on our branding, public image, and even ongoing consumer design initiatives."

![GlassView website section featuring the platform's case studies, designed by Designatives](https://ipu7rtrtpzxvlstg.public.blob.vercel-storage.com/product-team-glassview.webp)

## How to start without a big commitment

Start with one real piece of work: a feature, a fix or the first screens of a new product, shipped to production. It shows you how the team works before you commit to more. From there, run weekly sprints with demos, keep the code in your own repository from the first commit, and agree up front how a handover to your own team would work.

If you are weighing a first hire against an outside team, [tell us where the product is today](https://www.designatives.com/contact). You can also see how our [product development](https://www.designatives.com/our-services/product-development) works and how we work with [startups and SaaS companies](https://www.designatives.com/startups-and-saas).

## Questions about external product teams

### When should a startup use an external product team?

When you need a first version before you can hire, need skills such as product design, mobile or AI only part of the time, have a fixed launch or raise date, or need to take over a product someone else built.

### Is an external product team cheaper than hiring in house?

For a first version or for skills you need part time, usually yes, because you skip months of recruiting and pay only for the people the roadmap needs. Once the work is steady enough for several full time roles, an in house team usually costs less over time.

### How long does an external team take to build an MVP?

A first version typically takes eight to twelve weeks, planned in weekly sprints with a demo at the end of each, so there is something to review every week.

### Who owns the code when an external team builds the product?

You should, from the first commit. Ask for the work to live in your own repository and accounts, documented as it goes, so your own engineers can take it over without a rewrite.

### Can an external product team work with our in house developers?

Yes. The team joins your Slack, your repository and your sprints, takes work from your backlog and ships through your code review and release process.

Source: https://www.designatives.com/blog/external-product-team-vs-in-house
