← All offers Ayush Jain · Portfolio ↗

14-Day Launch-Ready Sprint · design & engineering

Built it with AI?
Make it launch-ready
in 14 days.

I give your app a look of its own, fix the agreed security risks, and rebuild the three flows that decide whether people stay. Design and code, by one person.

For an existing app. A reserved start, ready access and an agreed scope make the two weeks possible.

Sound familiar?

It works.
But it isn’t ready.

  • It looks like every other AI-built app.
  • You’re not sure who can see whose data.
  • People sign up, look around, and don’t come back.
  • Every fix seems to break something else.

You may not need a rewrite. You need someone who can work on the look and the code at the same time.

The aim of the two weeks

An app you’re
proud to show.

A clear first impression, journeys that make sense and tested fixes for the launch risks we agreed to tackle. A working product you can put in front of users and investors.

The look.
The flows.
The code underneath.

Up to three agreed flows and around twelve screens in total. We name the work before the clock starts.

A new look.

Type, colour and components that make the app feel like yours. I apply the direction to the agreed screens in your code, with responsive layouts and a visual review on day five.

Lockdown.

Scoped authentication, data-access and payment fixes. Where relevant, I test account separation by trying to access one test account’s data from another. The agreed priority fix ships within the first 48 hours of the reserved start, with access ready.

Three rebuilt flows.

Usually onboarding, the product’s main task and payment. Three to five user conversations inform the changes; you arrange introductions to people who can take part. The journeys are redesigned and rebuilt in working code.

Launch Dashboard.

Analytics on the steps that matter, error tracking and alerts, phone checks, deployment and a handover video. You keep a fixes checklist and a plain list of anything outside the agreed scope.

Lockdown is agreed remediation, not a comprehensive security audit or certification. If there is no suitable security priority, we agree another priority fix before starting.

Useful after
the launch, too.

AI style guide.
Design settings and examples your team and AI tools can use, so the next screen starts from the same visual decisions. Generated work still needs review.
User Voice report.
What the three to five people we spoke with said, what it means for the product, and what to consider next.
Launch Kit.
A refreshed landing-page header and social images in the new direction. Included free when a paid Check leads to a Sprint booking within seven days of the Check handover; otherwise a quoted add-on.
30-day fix warranty.
I fix defects in the delivered, agreed scope for 30 days after launch. It excludes new features, later scope changes, client changes to the delivered code and third-party failures.
Distribution plan.
A one-page plan informed by how I shared and grew Leetify: the audience, places to reach them and a useful launch message. A plan for your app, with no promised growth result.

Fourteen days.
Work you can see.

A tactile paper illustration of an idea becoming a working product
  1. Days 1–2

    Understand it.
    Fix the priority.

    User conversations, first-use review and the most important agreed engineering fix.

  2. Days 3–5

    Give it a look
    of its own.

    The visual direction, shown in real screens. You review the look on day five.

  3. Days 6–11

    Make the journeys work.

    Your three core flows rebuilt in pieces you can click through and respond to.

  4. Days 12–14

    Check it.
    Ship it. Hand it over.

    Analytics, phone testing, agreed release checks, launch and a handover video.

About three hours of planned founder time: kickoff, user introductions, the look review and launch. A short progress video every two days keeps you close to the work.

Two promises.

A look you want to show.

If you don’t like the direction at the day-five review, I redo it once, free, within the agreed screen scope.

Live on the agreed date.

Live in fourteen calendar days, with the agreed content, access and user introductions ready on day one and consolidated replies within one day.

If I’m late, ₹5,000 / $150 is credited per Monday–Friday working day, capped at 10% of the agreed Sprint fee. At list price, that is ₹25,000 / $600. Client-blocked days shift the agreed date.

Credits reduce the total service fee: I deduct them from the balance and refund any overpayment. We confirm the scope, inputs, review dates and release plan in the quote.

Who’s doing the work

One person.
Both sides of the product.

I’m Ayush, a product designer and engineer. I designed, built and launched Leetify, a Codeforces workspace listed at 20,000 users and 4.3 out of 5 on the Chrome Web Store.

I’ve also worked at startups as a founding software engineer, product manager and design lead. I use AI tools for speed; the judgement, implementation and release checks are my responsibility.

See the Leetify case study

Leetify is my real, shipped product. The three other portfolio projects are self-initiated concepts for fictional businesses.

The Sprint

₹2,50,000

International $6,000

Plan my Launch-Ready Sprint

Clear scope.
A reserved start.

Half to start, half at launch. Other payment schedules can be agreed in the quote. Applicable taxes and third-party costs are itemised before we begin.

A paid Launch-Ready Check comes off a Sprint booked within 30 days of Check handover. The credit is the actual retained fee after any refunds, used once against the Sprint fee.

First three clients: ₹1,75,000 / $4,200, with an agreed case study and permission to show the work. We agree what can be shared; feedback never has to be positive.

Up to two Sprint starts a month, on the 1st and 15th. This shares one calendar with ongoing clients and other projects. I confirm an available start before booking.

A focused upgrade
for a working product.

A few questions.

Do you use AI?

Yes, to move faster. The design decisions, code review and agreed testing are mine. I explain what changed and why in plain words.

Will you move me off Lovable, Bolt or Emergent?

Only if the agreed work needs it. Usually I work with what you already have. We identify any platform limitations before reserving the Sprint.

How will you work with my data?

We agree access, test data, backups and a release plan before starting. I work on a separate version where the setup allows it, use the access needed for the agreed work and confirm backup and restore arrangements before changes to a live database.

What happens after launch?

You can stop with the handover and 30-day fix warranty, or continue with Ship Every Week: design and code, one request at a time, up to 30 hours a month. ₹1.5 lakh / $3,500 per month, billed in advance. Ongoing capacity is confirmed separately.

What if I’d rather start smaller?

The 3-Day Launch-Ready Check is ₹20,000 / $500. You get a recorded walkthrough, ranked issues, one key screen rebuilt as a review prototype and a written fourteen-day plan. Five actionable problems worth fixing, or the Check fee is refunded.

Show me what
you’ve made.

A product link and the thing you’re unsure about are enough to start.

Book a Launch-Ready Check ayushhhudd@gmail.com