ABOUT TESTED WORKS

We built products ourselves. The lessons now shape how we build yours.

Tested Works was founded by Mikhail Feigelman and Miks Vasiljevs after building and operating Eyezilla and ZapFolder. We now bring the same product judgement, engineering ownership and production experience to client teams.

WHY TESTED WORKS EXISTS

We wanted the technology partner we had needed ourselves.

Eyezilla and ZapFolder began as very different product ideas. Building them exposed the same reality: a convincing prototype is only the beginning.

The difficult work lives between users, business rules, data, integrations and the unpredictable conditions of real operation. Tested Works exists to help other teams navigate those decisions without having to assemble a complete product and engineering department internally.

  1. 01

    EYEZILLA

    Building beyond the model

    Building a multi-site computer vision platform taught us that the difficult work begins after the model performs: unreliable inputs, edge deployment, privacy, monitoring and real operational use.

  2. 02

    ZAPFOLDER

    Making complexity understandable

    Building a collaborative SaaS product taught us how much product judgement matters: what to remove, what to automate and what users must still understand and control.

  3. 03

    TESTED WORKS

    Bringing that ownership to client systems

    We created Tested Works to give client teams direct access to senior product and engineering ownership—from uncertain first decisions through production operation.

THE FOUNDERS

The people behind Tested Works.

Mikhail and Miks lead every engagement together. Their responsibilities differ, but product, technical and delivery decisions remain shared.

Mikhail Feigelman, co-founder of Tested Works

CO-FOUNDER · PRODUCT, DESIGN AND SOFTWARE

Mikhail Feigelman

Mikhail leads product definition, UX and full-stack delivery. Through Eyezilla and ZapFolder, he has worked from early product uncertainty through interface design, engineering and real operational use.

On client projects, he focuses on turning complicated workflows into clear products, deciding what a useful first release must contain and connecting AI capabilities to the people and processes around them.

PRODUCT DIRECTIONUXFULL-STACK SOFTWAREAI WORKFLOWS
Miks Vasiljevs, co-founder of Tested Works

CO-FOUNDER · ARCHITECTURE, SYSTEMS AND DELIVERY

Miks Vasiljevs

Miks combines enterprise consulting experience from IBM with years building the infrastructure, integrations and backend systems behind Eyezilla and ZapFolder.

On client projects, he leads technical architecture, backend engineering, cloud infrastructure and production reliability—the parts that determine whether a promising product continues working as usage and complexity grow.

ARCHITECTUREBACKEND SYSTEMSINTEGRATIONSCLOUD OPERATIONS

Specialists join when needed. Accountability stays with the founders.

Additional design, engineering, data or domain expertise can be added around the work while Mikhail and Miks retain product ownership, technical oversight and direct communication.

WHAT EXPERIENCE CHANGED

Three principles we bring to every project.

These principles came from decisions that succeeded, assumptions that failed and systems that became difficult only after people began relying on them.

Evidence before expansion

Define what must become true for the work to create value, then build the smallest coherent system capable of producing that evidence.

Expose difficult conditions early

Integrations, permissions, exceptions and unreliable inputs should become visible before they turn into late-stage surprises.

Production is part of the product

Monitoring, evaluation, support and improvement are designed into the system rather than added after launch.

FOUNDER-BUILT PRODUCTS

Products we have built and operated ourselves.

Working with TW was an absolute pleasure. We hired them to build the MVP for an AI-powered Computer Vision platform and they exceeded all expectations.

Riccardo C. · GKM Tech · Verified Upwork review · 5.0

PROJECT INTAKE

Bring us the problem before you have the specification.

Tell us what needs to work, who it affects and what remains uncertain. We will help identify the smallest useful first phase.