R&D as a serviceProof of concept

    Proof of concept development: prove the one thing your product depends on

    Short answer

    A proof of concept is a working prototype that proves the one thing your product depends on, measured against an acceptance plan you sign before we build. We build it in two-week sprints with acceptance criteria you sign, and the prototype, code and documents are yours. A prototype is not a production launch: when it passes, the next step is the build.

    R&D as a service
    At a glance
    Provesthe one thing your product depends on
    Measuredagainst the acceptance plan you sign
    Processtwo-week sprints, acceptance criteria you sign
    PriceFixed price per written scope
    You ownprototype, code, documents

    What you get

    What a proof of concept gives you

    • A working prototype. It proves the one thing your product depends on, and nothing more.
    • A result against the plan. The prototype measured against the acceptance plan you signed before we built it.
    • A written recommendation. Go, change or stop, with what the build needs next.
    • Your code and documents. The prototype, its code and documents go to your repositories.

    How it runs

    From open question to a working prototype

    Your pathEach step is accepted in writing
    1. 01Questionthe unknowns · written downaccepted whenthe unknowns are written as questions you agree with
    2. 02Acceptance planhow each option · is measuredaccepted whenyou sign how each option will be measured
    3. 03Prototypetwo-week sprints · signed criteriaaccepted whenthe prototype has a result against the plan
    4. 04Decisiongo, change · or stopaccepted whenyou have a written recommendation: go, change or stop

    Fit

    When a proof of concept fits

    Use it when you

    • have a product that depends on something nobody has proved yet: ranging accuracy, proof cost, resistance to an attack
    • need hardware, firmware, cryptography and chain engineers who work as one team
    • must show evidence to investors or a board before the next round of spending

    Skip it when

    Proof

    Work behind this format

    R&D as a service
    Study and prototype

    Proof of humanity with zero-knowledge proofs

    Problem
    Bots drained airdrops and DAO votes; KYC was not an option.
    Built
    A feasibility assessment, then a proof-of-concept prototype.
    Scale
    Six trust levels, L0 to L5
    Zero-knowledge proofsProof of conceptGroth16Halo2
    Working prototype; protocol split into MVP and ZK phases.
    MVP · Location proof

    Proof of location, built on sensor fusion

    Problem
    Prove where a device is without trusting the device.
    Built
    Signal-harvesting mobile apps, token contracts, Java back end.
    Proof of locationSensor fusionEthereumEOS
    MVP and token contracts that reward confirming nodes.
    System · Devices

    Devices that prove where they are

    Problem
    Signed proof of physical presence that nobody can fake.
    Built
    Rust firmware on ESP32-C6, radio lab research, signed proofs.
    RustESP32-C6Embedded firmwareWi-Fi FTM
    Firmware to chain, signed off sprint by sprint.

    FAQ

    Questions buyers ask

    Q01Is a proof of concept ready for production?

    No. It proves the one thing your product depends on. When it passes, the build is the next step, run by our R&D team on your product or with dedicated engineers.

    Q02What if the answer is no?

    Then the study did its job before you paid for a build. You keep the evidence and the options that remain.

    Q03Who owns the results?

    You do. Results, code and documents go to your repositories.

    Q04Do you publish results from our work?

    No. We publish nothing from client research, and we name a client only where the client agreed.

    Q05Do you have your own lab?

    Yes. We test radios and sensors in our own hardware lab, each against a written acceptance plan.

    Q06How is a proof of concept priced?

    A proof of concept has a fixed price per written scope.

    Next step

    Book a call with Mykhailo and an architect

    A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger