Frequently asked

Honest answers about how we work.

Everything we get asked on a first call, scope, pricing, timelines, the parts that usually go wrong. If something is missing, ask us directly.

How we work

What does a first engagement actually look like?

A discovery call with the team, then a written kickoff brief with scope and a milestone map, then the work. The first paid milestone usually lands inside week three.

How do we trust the timeline?

Every engagement starts with a fixed scope and a milestone map, no vague sprints, no scope creep. We publish a kickoff brief before any work begins, and you review every milestone before we proceed. If a milestone slips, we tell you within 24 hours and update the map.

What's a typical engagement length?

Most Full Build engagements run 8–16 weeks from kickoff to live. Embed engagements run in 4-week cycles with explicit renewal points. Discovery reviews are free and don’t require a call.

How do milestones work?

We break the scope into 3–6 milestones with explicit acceptance criteria. You review and sign off on each one before we move on. If a milestone fails review, we revise on our time.

Pricing & engagement models

How do you price work?

We price the engagement, not the hour. Every scope gets a fixed price tied to milestones, so you know what you’re paying before any work begins. No hourly billing, no time-and-materials surprises.

What's the minimum engagement size?

Full Build engagements typically start at the size of a 6-week MVP scope. Embed engagements start at a single 4-week cycle. Discovery reviews are always free.

Do you take equity?

Occasionally, for the right early-stage team and the right structure. It’s never a substitute for cash, we want skin in your game, not a discount on ours.

Compliance & security

Do you handle SOC 2 / HIPAA / ISO 27001?

Yes, and we run it in parallel with the build. By the time your product is code-complete, your evidence package and policy set are already drafted and ready for audit prep.

Will I own the code and IP?

Yes. All source code, infrastructure, design files, and documentation are yours from day one. We deliver into your repos, your cloud accounts, and your tools, not ours.

Tooling & process

How is this different from Cursor, GitHub Copilot, or AI app builders like Lovable and Blitzy?

Cursor and Copilot are engineering productivity tools that make individual developers faster. AI app builders like Lovable, Base44, and Blitzy are platforms for generating prototypes or automating an existing codebase. modulaa is a delivery team that owns the whole product surface, product strategy, design, engineering, compliance, and go-to-market. We use AI throughout, but the output is a shipped production system, not faster code.

We're early-stage. Is this for us?

Possibly. We work best with teams that have a clear problem, a target user, and a 90–180 day runway to ship something real. If you're pre-idea, we’re probably too early. If you're post-idea and need to ship fast without building a 15-person team, that’s exactly what we do.

Do we need to replace our existing team?

No. modulaa is designed to work alongside product, engineering, design, and compliance teams. Most engagements amplify existing capabilities rather than replace them.

Can modulaa build a custom platform for us?

Yes. Many organizations engage modulaa to design, build, modernize, or extend custom software platforms. We can deliver a complete solution or work alongside your internal teams.

Who maintains the software after launch?

Every modulaa engagement includes documentation, architecture decisions, operational knowledge, and governance artifacts generated throughout delivery. Clients can operate independently, have modulaa provide ongoing support, or use a hybrid model. Because knowledge is codified throughout the lifecycle, long-term maintenance is not dependent on a small number of individuals.

What types of projects are the best fit?

modulaa works best on: custom software platforms, internal business systems, AI-enabled applications, platform modernization, digital transformation initiatives, and regulated software environments.

Methodology & positioning

What is parallel delivery?

Parallel delivery is a software delivery methodology where discovery, build, governance, and launch readiness run on a single shared clock instead of as sequential handoffs. In a traditional model, design finishes before engineering starts, code completes before compliance reviews begin, and each phase waits on the last. In parallel delivery, those phases advance together, guided by shared context and explicit milestone gates. The result is a production-ready release in weeks instead of quarters.

How is parallel delivery different from agile or sprints?

Agile reduced the size of each sequential cycle. Parallel delivery removes the sequencing. In an agile sprint, the work is still design → build → test → review, just compressed. In parallel delivery, those phases run concurrently across the same milestone, with senior contributors maintaining shared context. Agile works inside an existing operating model. Parallel delivery changes the operating model so AI-augmented contributors are not bottlenecked by sequential handoffs.

How is modulaa different from AI app builders like Lovable, Base44, or Blitzy?

AI app builders are self-serve platforms, you describe what you want, the platform builds it, you operate the platform license. modulaa is a senior-led delivery service. We use AI throughout, but the engagement is run by experienced operators on your roadmap, with fixed-scope pricing and parallel delivery covering discovery, build, governance, and launch. Builders are great for prototypes and low-stakes apps; modulaa is built for production systems that need real architecture, integration, and compliance work.

What does "Orchestrate · Codify · Govern" mean?

Orchestrate runs every delivery phase on a shared clock so discovery, build, design, and compliance advance together. Codify turns the decisions, patterns, and standards each engagement produces into reusable assets that accelerate the next engagement. Govern keeps compliance, security, and audit-readiness on the same timeline as the build instead of bolting them on after launch. Together they describe the operating model modulaa uses internally and delivers for clients.

How do modulaa engagements compare with platform licenses?

A platform license is a recurring contract for tooling, your team still needs to operate it. A modulaa engagement is fixed-scope work delivered by a senior team, priced once for an outcome. For example, a Custom Platform Delivery engagement is $250K–$600K all-in for 8–24 weeks. Enterprise platform licenses commonly start in the $500K/year range and grow from there. The right answer depends on whether you need a tool to use long-term or a partner to run a defined initiative.

Didn't find your answer?

Send us the question directly, we read every message and reply within one business day.

Ask us anything →

Production-ready software. Live in weeks.

Book a 30-minute call with the modulaa team. Tell us what you are building, where you are stuck, or what you need live. You leave with a one-page summary. Free, no commitment.

Book a call