Founder-led, with direct technical ownership.

Mariano Tami leads Pi Development and remains responsible for product definition, architecture, implementation, deployment, measurement and ongoing improvement.

Mariano Tami · Founder

Mariano is a self-taught software developer and AdTech practitioner with experience across digital marketing, analytics, SEO and web measurement. He works professionally in English and is a native Spanish speaker.

Background

From aviation to digital systems

Before entering technology, Mariano trained in civil aviation and worked as a commercial pilot. That background supports a systems-oriented approach to preparation, constraints, testing and clear responsibility.

Transition

A practical path into technology

During the pandemic, Mariano began studying digital marketing, web development and programming. His initial digital work included SEO and landing pages, followed by marketing specialist and marketing leadership roles for a language-education organization.

Delivery

Direct technical ownership

Mariano personally connects problem discovery, product definition, architecture, frontend and backend implementation, infrastructure, analytics, AdTech, QA, documentation and maintenance.

Delivery model

Founder-led by design

Pi Development does not currently have a standing team. When a project genuinely requires additional expertise, collaborators may be incorporated with their responsibilities made explicit.

Fit

Useful, maintainable and responsibly operated

Pi works with people committed to building a useful product and operating it responsibly, including founders, local businesses, operations teams, publishers and monetization teams.

Availability

Buenos Aires · Remote

Pi Development is based in Buenos Aires, Argentina, and available for remote work. Capacity is deliberately limited and depends on the complexity and responsibilities of each project.

Clear enough to explain. Strong enough to operate.

  1. Define before building

    Understand the user, operation and outcome before selecting technology.

  2. Use evidence

    Prefer working software, observable behavior and explicit constraints over claims.

  3. Keep ownership direct

    Maintain the connection between the business problem and its implementation.

  4. Prepare for iteration

    Build a maintainable base without pretending the first version knows everything.

A clear problem is a useful starting point.

Tell us what needs to be launched, automated, repaired or made easier to operate.

Bring us the problem