How much does a project cost?

Pricing depends on scope and availability. After a conversation, we prepare a proposal with deliverables and terms. If the problem needs more definition, we quote that phase first. We bill in US dollars.

How long does a typical project take?

We agree on timelines after defining scope and confirming availability. The proposal specifies deliverables and dates; we communicate the impact of risks or scope changes in writing.

What technologies do you work with?

Mostly TypeScript across the stack: Next.js and React on the frontend, Node.js or Python on the backend, and Postgres for data. We pick the stack for your problem, not the other way around.

Who owns the code and IP after the project?

Intellectual property ownership and usage rights are agreed in writing before each project starts. The contract defines what is transferred, what is licensed, and which components each party retains, together with handover and continuity terms. Attribution, such as “Developed by MuyuSoft,” and permission to feature the project in our portfolio are agreed separately.

How do we communicate during the project?

We agree on a communication channel, a contact on each side, and a progress schedule. Decisions, risks, and scope changes are recorded in writing. We coordinate working hours from Ecuador.

Do you offer support after launch?

The contract defines a warranty period for fixing defects attributable to our work at no extra cost. Maintenance and further development are agreed separately. We hand over documentation and access so another team can take over.

How exactly do you use AI in your process?

We use AI to assist with code, tests, and documentation. A person reviews and takes responsibility for every change. Architecture and product decisions remain with the team, and quality checks run before delivery.

Custom software · From Ecuador

Custom software built to last.

We are four engineer-founders. Work directly with the people building your application, with written scope, tests, and documentation so another team can maintain it.

Book a call Explore demonstrations

Our approach

How we actually build

Written scope, quality checks before delivery, and progress you can try yourself. Decisions and risks are documented.

We discuss the problem and agree on scope before writing code. If more discovery is needed, we propose a paid definition phase.

From the problem to an agreed scope

01 / From idea to product

“We need to organize our requests.”

One place to receive, review, and track every request from the team.

◈ Request portalFirst prototype

Requests+ New

Design teamReceived

Platform accessIn review

Illustrative projectILLUSTRATIVE DEMO

AI supports our work. An engineer reviews and understands every change; tests and automated quality checks are required before delivery.

Speed with engineering accountability

02 / Speed with judgment

Create a requestChange reviewed

Engineering review

Before saving, we check that the user has access to this team.

✓ Correction incorporatedApproved by engineering

Illustrative projectILLUSTRATIVE DEMO

We agree on the documentation, tests, and access needed to operate and maintain the system. Intellectual property ownership and usage rights are defined in each contract.

The freedom to choose your next step

04 / Ready to keep growing

A handover with clear terms.

Documentation and access under the agreed scope.

Source codeRepository and versions

DocumentationArchitecture and deployment

TestsCore flows covered

AccessInfrastructure and services

✓ Ready to hand offRights agreed by contract

Illustrative projectILLUSTRATIVE DEMO

muyusoft / workspaceIllustrative project

01 / From idea to product

“We need to organize our requests.”

One place to receive, review, and track every request from the team.

◈ Request portalFirst prototype

Requests+ New

Design teamReceived

Platform accessIn review

An idea starts taking shapeILLUSTRATIVE DEMO

The same project, from start to finish.Scroll to explore

01 / Idea

Understand first, then build

We discuss the problem and agree on scope before writing code. If more discovery is needed, we propose a paid definition phase.

From the problem to an agreed scope

01 / From idea to product

“We need to organize our requests.”

One place to receive, review, and track every request from the team.

◈ Request portalFirst prototype

Requests+ New

Design teamReceived

Platform accessIn review

Illustrative projectILLUSTRATIVE DEMO

02 / Judgment

AI drafts, engineers decide

AI supports our work. An engineer reviews and understands every change; tests and automated quality checks are required before delivery.

Speed with engineering accountability

02 / Speed with judgment

Create a requestChange reviewed

Engineering review

Before saving, we check that the user has access to this team.

✓ Correction incorporatedApproved by engineering

Illustrative projectILLUSTRATIVE DEMO

03 / Visibility

You see it before you ask

We share progress you can try and document decisions, risks, and scope changes. We agree on a demo schedule with you.

A product you can test and comment on

03 / Progress you can explore

staging.project.example

◈ Request portalProgress demo

Requests+ New

Design teamApproved

Platform accessReceived

YOU

Can we filter by team?Product feedback · Next iteration

Illustrative projectILLUSTRATIVE DEMO

04 / Handoff

Built to hand off cleanly

We agree on the documentation, tests, and access needed to operate and maintain the system. Intellectual property ownership and usage rights are defined in each contract.

The freedom to choose your next step

04 / Ready to keep growing

A handover with clear terms.

Documentation and access under the agreed scope.

Source codeRepository and versions

DocumentationArchitecture and deployment

TestsCore flows covered

AccessInfrastructure and services

✓ Ready to hand offRights agreed by contract

Illustrative projectILLUSTRATIVE DEMO

Services

One engineering team.
Three ways to start.

From your first hypothesis to a growing product. Choose where you are today.

Service 1 of 3

01 / VALIDATEBy agreement

I want to validate an idea.

Prototype

You get: A clickable prototype of the core flow
Goal: Test your idea with users
Format: A sprint with a defined scope

Quoted to scope

USD · One-time

Validate my idea

02 / BUILDBy agreement

I want to launch a product.

Custom product

You get: A production-ready product
Goal: Launch and operate your solution
Format: Agreed capacity and deliverables

Quoted to scope

USD · Per project

Build my product

03 / EVOLVEBy agreement

I need engineering capacity.

Continuous team

You get: Direct collaboration with the partners
Goal: Maintain and evolve your application
Format: Ongoing collaboration by agreement

Quoted to scope

USD · Per month

Extend my team

Scope, availability, timelines, and terms agreed in writing before work starts. We bill in US dollars.Not sure which to choose? Let's figure it out

Team

Four technical partners, one accountable team

We are four partners in Ecuador, and you work directly with the people building your software. Muyu means seed in Kichwa: something that starts small and is built to last.

Matheo Chávez

Co-founder & CEO · Full-Stack Engineer

Anthony Cochea

Co-founder · Backend & Infrastructure Lead

Juan Aristizabal

Co-founder · Frontend & UX Lead

Andrés Loza

Co-founder · QA & Delivery Lead

Demonstrations

Explore how
your application could work.

Two illustrative scenarios to explore interfaces and workflows. They do not represent client projects or measured results.

◈ supply / workspaceNorth plant

Procurement overview THIS WEEK

Requests243 connected sites

Approved18Role-based workflow

To review06Assigned to the team

REQUEST	TEAM	STATUS
Production materials	Operations	Approved
Safety equipment	North plant	Approved
Line spare parts	Maintenance	In review

✓

Order synced with the ERPNo manual data reentry

Concept demonstration · Fictional data

PROCUREMENT / DEMONSTRATION

Purchasing and approvals in one place.

A fictional scenario exploring requests, suppliers, and role-based approvals.

Purchase requests Role-based approval

Illustrative workflow

React · CSS

Explore demonstration

Concept demonstration · Fictional data

LOGISTICS / DEMONSTRATION

Routes and deliveries in one view.

A fictional dispatch and tracking scenario with a mobile driver interface.

Plan routes View deliveries

Illustrative workflow

React · CSS

Explore demonstration

01 / 02Explore the demonstrations

How we start

A simple first step.
A clear path to your demo.

From the first conversation to a delivery you can try. We agree on scope, dates, and terms before starting.

Tell us your idea.
30 minutes to understand your goals, constraints, and timeline.
Agree on the scope.
You receive a proposal with defined deliverables, timelines, and pricing.
We start building.
We start on the agreed date, with signed scope and an advance or first milestone payment.
Try it for yourself.
Real functionality in a staging environment, ready for your feedback.

01 / CONVERSATION

We start by understanding.

You do not need a specification. An idea, a problem, or a process you want to improve is enough to start a conversation.

30 minutes · Free

FIRST CONVERSATION30 MIN

Your idea + our teamSample agenda

The problem you want to solve10 min

Goals, context, and constraints15 min

The next step5 min

Stages depend on the agreed scope and availability. The deliverables shown are illustrative.

Tell us what you want to build

FAQ

Frequently asked questions

The essentials on investment, timelines, and how we work with you.

Have a more specific question?

Let's talk about your project

Let's talk

The next great idea
could be yours.

Tell us what you want to solve. You do not need all the answers to take the first step.

One of our four partners repliesWith a clear next step.

We review your idea and the context you share.
We email you to clarify questions and arrange a call.
In 30 minutes, we work out where to start together.

Prefer to email us directly?

contact@muyusoft.com From Ecuador · For founders and businesses in Ecuador, the US, and Europe

A little context.

THE FIRST STEP

Custom software built to last.

How we actually build

01 / IdeaUnderstand first, then build−

02 / JudgmentAI drafts, engineers decide+

03 / VisibilityYou see it before you ask+

04 / HandoffBuilt to hand off cleanly+

Understand first, then build

AI drafts, engineers decide

You see it before you ask

Built to hand off cleanly

One engineering team.Three ways to start.

I want to validate an idea.

I want to launch a product.

I need engineering capacity.

Four technical partners, one accountable team

Explore howyour application could work.

Purchasing and approvals in one place.

Routes and deliveries in one view.

A simple first step.A clear path to your demo.

Tell us your idea.

Agree on the scope.

We start building.

Try it for yourself.

We start by understanding.

Frequently asked questions

How much does a project cost?+

How long does a typical project take?+

What technologies do you work with?+

Who owns the code and IP after the project?+

How do we communicate during the project?+

Do you offer support after launch?+

How exactly do you use AI in your process?+

The next great ideacould be yours.

A little context.

One engineering team.
Three ways to start.

Explore how
your application could work.

A simple first step.
A clear path to your demo.

The next great idea
could be yours.