EEntiko
Start a project

Approach

We write the brief down. Then we build against it.

Most failed projects are not missing features. They are missing conversations. This is the sequence we use so the requirement cannot quietly change shape.

A website layout on a monitor, with the HTML beside it and a phone on the desk

  1. 01

    Discovery

    Who the customer is, what must happen this week, and what “done” means. We write that down before we design. If the brief is still a feeling, we will not pretend it is a specification.

    • A conversation with the people who sell, pack, or support — not only the founder
    • A written brief you can correct, including what we will not do
    • How Tuesday already works: chats, sheets, the person who knows the exception

  2. 02

    Structure

    Sitemap, flows, and copy. You see the skeleton while it is still cheap to change. Decoration waits.

    • Pages and screens named, in order, with a job for each
    • Headlines in your language, not lorem
    • A choice of stack written down — Next.js, Shopify, native, RN — with reasons

  3. 03

    Build

    You review a live URL (or a TestFlight / internal build) in short passes. Feedback lands on the product, not in a forgotten thread.

    • Staging you can share with legal, merchandising, or the floor
    • Decisions recorded so the next week does not re-litigate the last
    • A named owner on our side who actually answers

  4. 04

    Aftercare

    Launch is a beginning. We tighten copy, fix the awkward cases, and stay reachable. The first broken form and the first “can we add a page” are part of the job.

    • Credentials, CMS guide, and repositories in accounts you own
    • The first production nits included — not a surprise invoice
    • A care arrangement if you want one; handover if you do not

How long, for what

A five-page site is not a commerce rebuild. An app is not a weekend. We will say so before we start — not after the deposit.

A marketing or brand website

Typically 6–10 weeks

Sitemap, writing, design, and a multi-page build. Launch includes metadata, sitemap, analytics, and a walkthrough for whoever will edit pages.

An e-commerce store

Typically 8–12 weeks

Catalogue structure, checkout (including COD and WhatsApp where it is how India actually buys), and the operations the warehouse will live with.

Custom software

Phased, after a two-week map

We encode how Tuesday already works: jobs, stock, bookings, catalogues. First slice ships usable. You own the code.

An Android and iOS app

A first installable slice in weeks, then a store train

Native or one codebase — written down with reasons. Play Console and App Store Connect in your organisation. The API stays in the same studio.

What we need. What you get.

  • From youAccess to the people who run the work — not only a deck

    From usA named owner on our side, and written decisions

  • From youExamples of what “good” looks like to you

    From usA sitemap or flow you can correct before we decorate it

  • From youHonest constraints — budget, season, staff, a hard date

    From usReviewable builds on a URL, not a slide

  • From youSomeone who can answer in a day

    From usLaunch support and a short aftercare window, scoped in the brief

If this is how you want to work, send the brief.

The practices this sequence applies to are on Services.

Start with a brief