How we work
Brief to shipped.
In two-week sprints.
Software, agents, brand, and campaigns move through the same system: a written scope, a senior lead, agents in the loop, and a demo twice a week.
Brief to kickoff
From brief to shipped in four steps
Send a brief, get a written scope, run the sprint, measure what it moved. No proposal decks, no discovery theatre.
- 1
Brief
Send the form or a DM on X. We reply within one business day with questions and a first read on scope.
- 2
Scope
A discovery week or a two-hour session produces a spec, a plan, and a fixed price. You sign the scope, not a retainer.
- 3
Sprint
Two weeks of build with demos on Tuesday and Friday. Everything lands in your repo and your portal as it ships.
- 4
Ship and measure
Launch, instrument, and review weekly. Extend with another sprint, move to a retainer, or stop with a clean handover.
Sprint board
Every change lands as a diff you can read. Nothing ships without a demo.
Principles
Six things we hold to
The rules that decide how every engagement runs. They are the same for a two-week sprint and a venture we own.
Ship every week
A demo is the unit of progress. If it did not ship, it did not happen.
Agents in the loop, people on the wheel
Agents write code, tests, copy, and variants. Senior people set direction and sign off before anything goes live.
One team
Engineering and marketing sit in one channel with one plan, so product decisions and growth decisions are the same decisions.
Measure everything
Every sprint has a number attached. Dashboards go live before the work does.
You own it
Code in your repo, ad accounts in your name, data in your infrastructure. Leaving is easy, which is why partners stay.
Small and senior
No layers between you and the people doing the work. A lead, a builder, and the agents they run.
The stack
What we run on
Boring where it should be boring, current where it matters. The same stack runs partner work and our own ventures.
TypeScript and Next.js
App Router, serverless and edge runtimes, static wherever the page allows it.
Serverless cloud
Functions, step workflows, and managed queues for backends that scale to zero and back.
Postgres and managed data
Supabase or DynamoDB depending on the shape of the data, with migrations checked in.
Frontier models
Several model providers behind one gateway, chosen per task and swapped without a rewrite.
Agent runtime
The Forge runs long-lived agents with tools, evals, and a receipt for every action they take.
Payments
Stripe for subscriptions, checkout, and usage billing, wired on the first sprint that needs it.
Observability
Traces, logs, and error tracking from day one. Alerts route to the shared channel.
Ads and analytics
Meta, Google, and X campaigns run as config and measured against revenue rather than clicks.
Standard sprint length
Brief to kickoff
Code and accounts owned by you
Track everything in the client portal
Sprint board, demo recordings, agent receipts, campaign dashboards, and invoices behind one sign-in. No status meetings required.
Two ways in
Envinyatan
For existing companies. Sprints, retainers, or both, with a fixed price before kickoff.
- Start with a discovery week or a single sprint
- Fixed scope and price on every engagement
- Your repo, your cloud, your ad accounts
- Move to a retainer when the work is continuous
Vinyatan
For new companies. We build the product, the brand, and the go-to-market, and we take a stake.
- Equity or revenue-share structures
- Product, brand, and growth built together
- Shared production system in The Forge
- Pitch in ten minutes through the form
Questions
How fast can we start?
Usually within a week of the brief. We reply within one business day, run a scoping call or a discovery week, and send a written scope and price. The sprint starts the next Monday once that is signed.
Who does the work?
A senior lead who owns the outcome, one or two builders, and the agents they run. Nobody hands your project to a different team after the sale. The people on the kickoff call are the people in your channel.
How do you use AI on our project?
Agents draft code, tests, copy, creative variants, and reports. Every action leaves a receipt in the portal, and a person signs off before anything reaches production or a customer. Our principles page describes the rules we follow on every engagement.
Do we own the code and the accounts?
Yes. Work lands in your repository, your cloud, and your ad accounts from the first day. If we set something up on your behalf, ownership transfers at handover, and that transfer is written into the agreement.
What happens if scope changes mid-sprint?
We swap, not add. New work replaces something of equal size in the sprint or moves to the next one. The price does not change inside a sprint. Between sprints, the roadmap and the quote are re-cut together.
Can you work inside our existing team and tools?
Yes. We work in your repo, your issue tracker, and your Slack. The portal mirrors what is there rather than replacing it. Your engineers review our pull requests, and we review theirs if you want a second set of eyes.
How do you handle security and data?
Least-privilege access, scoped credentials, and no partner data used to train anything. Access is revoked at handover. The security page lists the practices, and the DPA covers the terms.
What if a sprint does not ship?
Rarely, and never silently. If a sprint is at risk we say so at the Tuesday demo and cut scope to land something usable. If the miss is ours, the fix is on us. The agreement covers the details.
Send the brief.
One form. One business day. A written scope before any work starts.