Arkyn Labs

WORK

Engagements in flight.

Active engagements aren't published while they're underway — clients tend to prefer it that way. Below is one we can show, alongside what we're building in-house. For the rest, the strongest signal is what's already in The Lab — investigations, working notes, and the tools we build with.

DELIVERED

Emergency QR

An emergency medical QR built for a client — scan the code and a person's critical details (blood group, allergies, emergency contacts) surface instantly, with no app to install. Built as a PWA on Next.js, Supabase, and Razorpay; prototype delivered and shipped for client testing.

Read the case study

Things we've built or are building in-house. Separate from client engagements — these are studio projects where we set the brief, ship the work, and learn from doing.

STATUSIn build

Vouchtails

All-in-one platform for pet parents — community, vet services, sitter marketplace, retail. Chennai pilot launching first. Currently in build.

Most engagements start as a conversation, not a brief. Once the question is clear, we shape the scope around it. Here's how that typically runs.

  1. Scoping

    We start with a conversation, not a proposal. If the question fits what we do, we sketch the engagement together. If it doesn't, we say so and point you elsewhere.

  2. Timeline

    Most engagements run two to six weeks. Anything shorter is usually a focused sprint or prototype. Anything longer is a multi-phase build.

  3. Deliverables

    Documents, prototypes, working code, or a working strategy — whatever the question needs. Scope decides format. Format isn't pre-baked.

  4. Billing

    Fixed price for scoped work. Hourly for exploratory phases. Always agreed before work starts. Invoiced on milestones, not retainer.

← Back to the studio