Questions about working with Hapy.

We work with founders, operators, and teams that need help building a product, improving software, or making their business systems work better. We also work alongside agencies and internal teams on a defined part of a project.

We are a good fit when you have a problem worth solving, can make time for decisions and feedback, and want a team that takes responsibility for the agreed work. You do not need a complete specification before we talk.

We may not be the right fit if you only need a small isolated task, need someone available as a permanent employee, or cannot make time to review the work. We will discuss the fit before proposing an engagement.

Hiring can make sense when you need a permanent role. For a defined project or a changing set of priorities, Hapy brings the relevant product, design, and engineering skills together without you having to recruit the whole team first.

We discuss what you are trying to achieve, what you already have, and the constraints. If Hapy can help, we will suggest a suitable next step. We may need to review your existing work before we can define the scope and price.

We help teams design and build software products, first releases, business systems, and AI workflows. We also connect existing tools, improve products already in use, and migrate websites to Astro.

Yes. Bring your idea, notes, pitch deck, or research. We can help define the first user journey, identify what needs to be learned, and agree on a useful starting scope.

Yes. We can review your designs or prototype, identify missing screens and decisions, and agree on what is needed to turn it into working software.

Yes. We can work with existing software, code, and workflows. We will review the starting point and agree on the changes before work begins.

Yes. We can take responsibility for a defined part of the work and coordinate with your designers, developers, agency, or project lead. We agree on responsibilities and communication at the start.

Yes. We help identify useful applications, connect AI to existing data and tools, and build agreed workflows. The work can include testing with real examples, human approvals, and handling errors.

Not usually. We review your current tools and workflows first. We can connect or improve what you have, subject to access and integration limits, and explain the options before agreeing on changes.

We focus on the core user journey and the main assumption you need to test. Together, we agree on what fits in the first release and what can wait.

Prices depend on the work and engagement. Published offers include the 45-day product sprint at $3,499 as a one-time fee, MVP development at $5,999 per month, and business systems and automation at $4,999 per month. Scope and other costs are confirmed before work starts.

Yes. Some projects have an agreed one-time price and scope. For work that continues or changes over time, we also offer monthly or quarterly engagements with agreed capacity and priorities.

Yes. We can discuss a focused first release or a defined part of a larger project. The right starting point depends on the problem, the work already done, and what you need to learn or deliver first.

We discuss the change and explain its effect on cost, timing, and priorities. Extra work is agreed with you before it is added to the plan.

This depends on the engagement. Hosting, paid services, licences, and other third-party fees may be separate. We will clarify the expected costs and what is included in your proposal.

Cancellation terms depend on your agreement. Our website terms state that invoices for weekly or monthly cycles are not refundable, whether paid before or after the work. Review the payment and cancellation terms in your agreement before work starts.

Hapy Co is the brand you work with. ENOU Labs LLC is the legal company behind the brand for contracts, invoices, and payment processing. You may see its name on your invoice or card statement.

The team depends on the work you need. Hapy brings in the product, design, engineering, AI, or operations specialists needed for the agreed scope. You work directly with the people responsible for delivery.

You get access to the project tools used for delivery. Tasks, updates, decisions, and feedback stay visible there. We also review the work with you and agree on how the teams will communicate.

We need a clear point of contact, access to the relevant materials and systems, and the people who can make decisions. Timely feedback helps keep the work moving. We will tell you what is needed for your project.

We agree on what the work must do before delivery. Depending on the project, testing can cover the agreed user journeys, integrations, and failure cases. You review the work and provide feedback before release.

Your scope sets out the handover, documentation, access, and any included support. You can continue with your own team or discuss further development and support with Hapy.

Our product build engagements state that you own the code and service accounts. The deliverables, ownership, and handover for your project are set out in your agreement.

Yes. We plan the handover around the team that will run the software. The agreed scope sets out the code, access, and documentation to be handed over.

We can discuss confidentiality requirements before you share sensitive materials. Any confidentiality obligations, including a non-disclosure agreement if needed, should be agreed before the work starts.

We review access, hosting, backups, connected services, and data location against your requirements when defining the work. The agreed controls depend on the project and provider. Hosting in a particular location alone does not establish compliance.

Third-party services, fonts, libraries, and other licensed materials have their own terms. We will clarify which services or licences the project needs and which costs or accounts are your responsibility.

Start dates depend on the scope, the people needed, and current availability. Tell us about your deadline on the first call and we can discuss a realistic start date.

It depends on the scope, integrations, access, and feedback. Our product sprint has a 45-day delivery period for an agreed first release, and eligible Astro migrations can be ready in two weeks after scope, content, and access are ready. We agree on milestones for other work after review.

Missing access or content, slow feedback, changes in scope, and unresolved decisions can affect the schedule. We will raise blockers as they come up and discuss their effect on the plan.

Tell us what needs to happen and when. We can review the scope and availability, then agree on what is practical within the time available.