Edgar Ortiz LLC

How I work

Every engagement runs the same five stages. You always know which stage you are in, what it produces, and what ends it.

  1. Discovery

    We establish what you need, your budget and timeline, who makes decisions, and anything that would stop the project. I send written questions and we talk them through.

    Ends when: we both agree it is worth planning in detail.

  2. Planning

    I turn what we learned into four documents: product requirements, a technical design, a milestone plan, and a proposal with a statement of work and payment schedule. If you arrive with your own specification, this stage is shorter, but the specification still gets reviewed before I commit to it.

    Ends when: the statement of work is signed.

  3. Implementation

    I build in slices tied to the milestones. You see a demo every week. Each milestone ends with your written acceptance, and acceptance is what triggers that milestone's payment.

    Ends when: every milestone is accepted.

  4. Deployment

    Before launch I work through a readiness checklist: you own every production account, monitoring and backups are live, credentials are rotated, the domain is cut over, and final testing and a security review are complete. You sign an acceptance certificate.

    Ends when: the acceptance certificate is signed.

  5. Post-Deployment

    A warranty period follows acceptance, 30 days by default and stated in your statement of work. It covers defects in what was delivered. Before it ends, we decide what comes next: close the engagement, start a support retainer, or scope a new phase.

    Ends when: the warranty closes and the next step is decided.

Written milestones and acceptance

Each milestone has a defined deliverable, a target date, and a payment tied to it. You have five business days to review a deliverable. Accepted work is the only work you are invoiced for.

Fixed fee

The price is set before work starts and does not move with the hours it takes. If you want something outside the signed scope, I write a change order at $140 per hour and you approve it before I start. Scope does not change silently and neither does the invoice.

Adversarial review

Before any plan or deliverable reaches you, it gets a separate review whose only job is to find what is wrong with it. That review looks for contradictions between documents, security problems, and work that does not match the signed scope. Problems are cheaper to fix before you see them than after launch.

Lean by design

I use AI tools throughout delivery: drafting, testing, and review. That is how one senior engineer delivers work that used to need a small team. The judgment stays with me. I scope, price, sign, and answer for every engagement.

Start with an email

Tell me what you want to build or decide. I will tell you whether I am the right fit.

edgar@edgarortiz.com