Vikika Team

The challenge

Vikika Team ran personalised nutrition on spreadsheets, PDFs and WhatsApp. The bottleneck was not getting clients: it was the nutritionist's work, hours spent building meal plans and reviewing check-ins. Any tool that buys time there has to be dense and precise — an unknown macro cannot be shown as zero, and a client restriction cannot slip past when a plan is published — while still giving the end client a mobile app they understand without instructions. Three very different profiles, one launch date.

The solution

We designed and built all three surfaces in a single codebase and took them to production in ten to twelve weeks. This is what shipped:

• Nutritionist backoffice. A plan builder by week and day, with macros in monospace so they compare down a column. If a food has no grams yet, the day says so instead of counting it as zero. The client's restrictions stay on screen while the plan is built and again when it is published. Around it: the client book, check-ins, templates, recipes, calendar and availability.

• Admin panel. The whole book of business: clients, check-ins, plans, staff, payments and settings. Admin is unrestricted. A nutritionist only reaches the clients assigned to them.

• Client app. Mobile-first. The client sees their plan, joins the Zoom call, answers the intake, weekly and renewal questionnaires, and follows their weight, measurements and adherence. Chat with the team lives in the same app.

• Infrastructure. Next.js, Supabase and Drizzle in a single codebase for all three surfaces. Permissions do not depend on whether a button was rendered: the check lives in the data-access layer, with RLS behind it.

• CI/CD. Continuous integration and delivery, from the change in the repository through to production.

• Stripe payments. Signup, pause and renewal. Billing is anchored to plan activation, not to the moment the client signs up.