MVP DEVELOPMENT & LAUNCH

Build an MVP you can launch and learn from.

We define the first product journey, build the software and prepare measurement. Landing pages, CRM and an acquisition test can be included in the agreed launch scope.

Discuss your MVP See the delivery process

Scope, schedule and investment are agreed after diagnosis. Media spend and third-party tools are listed separately.

THE PRODUCT'S FIRST QUESTION

Learn what people do with your first product.

Define the product, measurement and first acquisition test within one agreed scope.

  1. 01

    Scope grows before anything is validated

  2. 02

    Features ship without measuring how early users use the product

  3. 03

    Launch campaigns planned without the product journey in mind

  4. 04

    Analytics is added too late

  5. 05

    The founder has to coordinate several vendors

  6. 06

    Launch traffic arrives without signup, activation or usage data

PROJECT FIT

One team from product definition to launch.

A useful conversation starts with a user, a problem, a hypothesis and the conditions to learn from launch.

A good fit when

  • Businesses launching a new digital line
  • Founders who know their market and can reach early users
  • Manual operations where demand has already been demonstrated
  • Businesses with an audience, customer base or acquisition budget
  • AI-native products whose core value depends on a defined AI workflow, with a concrete user, problem and testable hypothesis.

A poor fit when

  • An idea without a defined problem or audience
  • A project without an internal owner
  • A search for the lowest price alone
  • An open scope without priorities
  • Equity as the only form of payment
  • Hourly developer allocation

DELIVERABLES

Deliverables matched to your product's first stage.

The proposal lists included deliverables and anything that depends on access, data or suppliers.

Product

  • Discovery
  • Ideal customer profile
  • Journey map
  • Prioritization
  • Prototype
  • UX/UI
  • MVP backlog

Engineering

  • Production application
  • Authentication and permissions
  • Database
  • Integrations
  • Infrastructure
  • Observability
  • Critical tests
  • Documentation

Launch

  • Landing page
  • Analytics
  • CRM
  • Funnel events
  • Launch plan
  • Initial creative assets
  • Pilot campaign
  • Sales cadence
  • Learning report

Paid media is a separate project cost.

PROCESS AND SCHEDULE

Define, build, launch and learn.

Diagnosis helps define scope, dependencies, schedule and acceptance criteria before the build starts.

  1. 00

    Discovery

    Schedule agreed in the proposal

    Quoted after diagnosis

    Interviews, market review, ideal customer profile hypothesis, prototype or core flow, risks, initial architecture, scope, schedule and first acquisition test plan.

  2. 01

    Product definition

    Schedule agreed in the proposal

    Journey, wireframes, design, acceptance criteria and measurement plan.

  3. 02

    Build

    Schedule agreed in the proposal

    Demonstrable deliveries, shared repository, tests, integrations and staging.

  4. 03

    Launch

    Schedule agreed in the proposal

    Deployment, instrumentation, landing page, CRM, campaign and supported operation.

  5. 04

    Learning

    After launch

    Review user behavior, interview users, prioritize the backlog and recommend next steps.

CONTRACTED OUTCOMES

  • Product in production
  • Agreed scope delivered
  • Funnel events working
  • Pilot campaign configured or run, if included
  • Usage data available
  • Learning report
  • Plan for next experiments
  • Documentation and project code delivered

RELATED EXPERIENCE

Product experience from our team's careers.

Explore the context, responsibilities and deliverables for each project.

PropTech

  • Product
  • Growth

PilarHomes

Lucas's professional experience

Context
A premium real estate marketplace within a PropTech operation.
Problem
The journey needed to preserve context and trust throughout property discovery, presentation and negotiation.
Lucas's role
RFC · Product · Frontend engineering · Production delivery
Solution
  • Property page and contextual navigation
  • Curated collections with named curators
  • Off-market flows
Outcome
A property discovery and presentation experience in production, preserving context throughout the journey.
Scale
Marketplace and real estate operations
Reliability decisions
Delivery from RFC to production
View project

PropTech

  • Platform
  • AI

Catalog Integrity

Lucas's professional experience

Context
Internal operations for property quality and availability.
Problem
Unavailable or outdated properties created noise and recurring operational review.
Lucas's role
Engineering leadership · Architecture · Backend · Observability
Solution
  • Multiple-signal analysis
  • Confidence-based rules
  • Asynchronous workers
  • Auditing and human review
Outcome
A catalog integrity operation combining automation, auditing and human review.
Scale
A continuously operated real estate catalog
Reliability decisions
Auditable restoration · Human review proportionate to risk
View project

PropTech / SaaS

  • Product
  • Growth
  • Platform

Superlógica

Lucas's professional experience

Context
An operations platform for condominium management and the real estate market.
Problem
Lead and search flows needed to become faster without disrupting the product in production.
Lucas's role
Analytics · Database · Frontend · Search · Web and mobile
Solution
  • Analytics-led improvements
  • Frontend modernization
  • Search improvements
Outcome
Lead, search and experience flows improved without interrupting the existing product.
Scale
A SaaS platform with web and mobile experiences
Reliability decisions
Incremental improvements · Continuity of the product in production
View project

Investment

Scope and investment

Quoted after diagnosis

We quote the work after diagnosis, based on the product, integrations, data and delivery requirements. The proposal lists deliverables, acceptance criteria, dependencies and responsibilities before development starts.

Discuss your project

Hosting, CRM subscriptions, AI usage, SMS and messaging charges, email services, data feeds and media spend are separate third-party costs unless the proposal explicitly includes them.

OUT OF SCOPE

Define what falls outside the scope.

Exclusions and external dependencies are documented before the project starts.

  • No guarantee of sales or revenue
  • Paid media, third-party tools and ongoing sales operations unless listed in the proposal
  • Open scope without priorities and acceptance criteria

PROJECT LEADS

Direct access to the people responsible for decisions and delivery.

Product and engineering stay with the people leading the project; marketing joins when the scope calls for it.

Lucas Pereira

Lucas leads product and engineering decisions and follows delivery directly. You work with him on the project scope and implementation.

Beatriz Lochel

Beatriz leads positioning, launch, CRM, creative direction and acquisition when those areas are part of the agreed scope.

Felipe Sarilho

Felipe manages the commercial relationship and connects business goals to project decisions.

COMMON QUESTIONS

Questions to help decide whether to talk.

Do you work for a fixed project fee?

Yes. After diagnosis, we define deliverables, milestones and acceptance criteria. Significant scope changes are assessed separately.

Do I own the code?

The client receives access to the repository and the project code, subject to the disclosed third-party components and licenses.

Do you only handle the technical work?

No. The scope can include discovery, UX, analytics, CRM, launch and initial acquisition. The exact scope depends on the product stage.

Do you guarantee sales?

No. We agree on deliverables, measurement and any contracted experiments. Revenue depends on the market, offer, price, acquisition and the client's operation.

Do you continue after launch?

A separate managed evolution phase can cover an agreed roadmap, improvements and new experiments.

Do I need an engineering team?

No. You need an internal owner who knows the business and can make decisions and validate the work.

Next step

What does your first product need to prove?

Share the audience, core journey and decisions you want to test. We will assess a practical first scope.

Discuss your project