from the lab · 15 september 2026
been building, forgot to write about it
a few months of mch, some client work, and the things still held together with WIP
by vismay hegde · meow creative haus
been a bit buried in the work lately
websites, enquiry flows, editors, then somehow a small fantasy world for dev logs
thought i'd put some of it here while i still remember why we changed things
first, 1clickwebsiteindia
for 1clickwebsiteindia, we've been working on a website builder for local businesses
the brief sounds simple enough: give the business its own page, let the owner understand what they're changing, make it work on a phone
the editor now has phone, tablet and desktop previews, section controls and bounded design remixes in the code
there's presentation editing taking shape too, with editable text, slide ordering and undo
still WIP, but this is the part i care about: can someone change a thing without feeling like they've broken the whole thing
small alpha from this one: put the preview close to the decision
“save” is a surprisingly large commitment when you have no idea what happens next
berglabs, and the journey after the post
with berglabs, part of the work has been around carrying useful context from a social post towards an enquiry
labelled links, first and latest visits, somewhere for that information to go
the new attribution work is prepared locally; the staging installation and CRM connection still need proving
one detail worth keeping: analytics consent and advertising consent are separate
saying yes to understanding a visit shouldn't quietly become yes to ad pixels
the website direction is changing too: four managed services up front, platforms and applications further in as evidence of how the work gets done
that is still being worked through
people arrive with a problem. making them learn the entire company vocabulary before they can choose anything is quite a tax
tender moments, especially reply two
tender moments has involved the website, parent-facing content and the enquiry process around it
clearer visit prompts, a compact testimonial section, and a lead register that puts age band, programme, care hours, start timing and area together
the staff still enters the enquiry. there isn't a magical inbox-to-sheet connection hiding here (yet)
right now, n+1 is the basic acknowledgement
after that, staff read what the parent actually said and follow up in their own words. pasting an LLM reply into that moment loses trust
the future path is a webhook into a database update, then support for n+2 and n+n replies without hiding the human inside the workflow
you find the missing information very quickly
the bits worth copying
the useful tools are small: a preview beside the edit, a labelled source link, a lead register that keeps the fields together, a second reply with a human in it, and an estimate that stays an estimate
copy the order before you copy the stack. put the decision in front of the person, keep the context attached, then leave a clear place to pivot when the answer changes
that is enough to start. the rest can earn its way in
the small instructions have a shelf now
some of the MCH in-house flow is now available through the skills section on the website
clear answer helps get to the point. keep my voice edits without sanding the writing flat. usable handoff makes the result easier for the next person to pick up
they are small instruction files built from repeated work, which is probably the right size for them
meanwhile, meow ops got a little carried away
what started as making dev logs readable is growing into an interactive 3d sanctum
the sanctum is being carried through blender work, with a local guide that has voice and mouth-animation work
session identity and usage now have a place in a world. the local guide has voice and mouth-animation work; character tests are happening separately while the full scene comes together
there's also a slightly strange personal-assistant idea in the mix: a krishna-inspired fren. e-krishna to e-arjuna (you), with the guide helping you look at the work without pretending to be the answer
very much WIP
also, estimated cost stays estimated cost. dressing a number up nicely doesn't turn it into an invoice
i like seeing an internal tool get a personality. i also want to be able to tell which session i'm looking at
both jobs remain
a zine escaped, and october has a token problem
tech+misc larp issue 01 is out
randomly fired, whenever there's something worth putting together
next month i'm planning to move most of the mch workflow towards hermes agent + kimi k3
the aim is lower token cost. the migration is WIP and the savings are still something to measure
cheap inference gets less exciting if i spend the evening repairing the output, so that'll be part of the experiment too
i'm also exploring Kunchenguid's Firstmate, Herdr and Lavish around agent supervision and visual review. that is exploratory too, not the new permanent stack
the little green squares
1,683 contributions in the last year, in this github snapshot
quite a lot of tabs behind those squares. some building, some fixing what i'd just built. keeping the screenshot here as a small receipt of time spent; the useful part is still whether the things work for someone else
lastly, patherle
patherle is about business conversations and the work those conversations create
the current workspace brings knowledge, conversations, campaigns and voice setup into the same place
one small change i like: new users get directed towards the next unfinished setup step; returning users keep the page they came back to
knowledge upload has files and pasted text, progress, parse errors and retry paths. website crawling is gated
there are a few friends-and-family businesses testing the beta now
the small-business agent is being shaped for sales, customer service and social media. that release sits further out, towards 2027, so the current work is still about finding the shape
there's more being built, but i'll leave it there for now
a lot of the recent work has been this sort of thing. making the next action clearer, giving someone a way back when something fails
less exciting to announce than a new feature, until you're the person trying to use it
anyway, back to the tabs
