
What Is Mike Michelini Up To Now: September 27 to October 3, 2026
I am back from Bangkok with Miles, and I feel like both of us came home with more than we packed.
I wrote a separate story about the full weekend, the Monsnatch launch, and what Miles and I are learning while building Snapchum: Snapchum Business Bonding Experience with Miles, Bangkok Card Launch.
We went for the Monsnatch experience and both joined the tournament. Miles reached the top 32, and I have his placement reported as nineteenth. That is our report from the event, not an independently verified official result, but the number is not really the part I keep thinking about.
I watched him meet people, play through pressure, and find his own way inside an unfamiliar environment. He is still young, and I am trying not to turn every experience into a business lesson. But being on the road together gave him a real look at products, events, relationships, competition, and the less glamorous work around all of it.
It also gave both of us another lesson in self-structuring. When nobody is standing over you telling you what to do next, how do you use your time? That question matters for a young person growing up, and honestly it matters just as much for me right now.
Crossing into Q4
This week we cross into Q4.
In China, Mid-Autumn Festival runs from September 25 to 27, followed quickly by the National Day holiday from October 1 to 7. For me, that period has always felt like a strong seasonal transition. The rhythm changes, messages slow down or bunch up, and then the final quarter arrives with all its pressure.
That is a personal observation from years of working around China, not an economic forecast. I just feel the shift. And this year, the mayhem is already getting started.
Learning the dual rail method
I have been calling my new way of working “dual rail.” I wrote a more detailed personal SOP at mikesblogdesign.com/dualrail.
The two rails are simple to name: Build and GTM.
Build is the product, development, systems, workflows, and quality control. GTM is the message, audience, relationships, outreach, follow-through, and learning whether the thing connects with anyone.
In the old rhythm, I would often separate these jobs. I would have a development day and tell myself marketing would happen later. Or I would stay deep inside one build until the session ended. The problem is that “later” can become a very long time.
Agents change the shape of the session. I can give one bounded thread a clear outcome, let the agent hold the context, and review the next move when it returns. While that rail is waiting, I can review the other rail. If a build is compiling or an agent is working through a defined task, I can check GTM follow-ups. If Bernie.agent is preparing a monitored relationship or social CRM draft, I can review a finished product diff.
The important word is review. This is not six tabs, endless context switching, or starting another product because I feel uncomfortable waiting. It is two named rails, bounded threads, and human quality control on both.
I am still learning it. Some sessions feel smooth. Other sessions feel like I am standing between two moving trains trying to remember which one needs me. I do not want to present this as a perfected system. It is a practice, and I am trying to get better at it.
Cross Border Summit is the real test
Cross Border Summit is now roughly one month away. We will be together in Chiang Mai from November 3 to 5.
It is a very real dual rail example because development and marketing cannot wait politely for each other.
On the Build and operations rail, we are working through systems, attendee experience, gifts, tracking, and workflows. On the GTM and relationships rail, we are working through speakers, attendees, promotion, outreach, and follow-through.
One of the encouraging parts has been watching the human and agent adoption around me. Snook has been stepping up strongly with Lisa.agent and the Grok-bot workflows. Bernie.agent is also developing into a monitored social CRM and GTM support layer. These are not replacements for people, and they are not unsupervised machines running the event. They are ways for the team to hold more context, surface the next move, and keep a human owner responsible for the decision.
There are still many things we have not solved. I am not going to claim the gifts are purchased, the attribution is perfect, or every workflow is finished. The useful part is seeing the two rails move together and learning where they still collide.
Making internet names useful
On the HeadlessDomains side, there is a lot happening around the partner program, new domain possibilities, improved onboarding, agent identity, and agent-to-agent commerce.
.c has gone live, but we held back the larger public promotion while improving the onboarding experience and the legacy-holder claim path. We have also been testing the GFAVIP Wallet modal SSO and the hardening around it. I would rather say something is being improved and tested than pretend every discussed extension, transfer, integration, or partner launch is complete.
The bigger idea still excites me. Identity and agent-to-agent communication are becoming important parts of the internet's next layer. A name should be more than something collectible. We are working to give these names practical utility, so people and agents can use them to identify, communicate, and eventually transact with more trust.
Some new partnership work is taking shape here too, but it is not ready for the private names, terms, or implementation details to become a public story.
Waiting under pressure
At the same time, I am still dealing with a marketplace verification and compliance review.
I completed the requested call and supplied the requested information. There has been no final adverse decision. Now there is waiting, and the timing is not in my control.
That is stressful. I believe our case is strong, but belief does not make the waiting easy. I also do not know whether our experience is unusual or part of something broader, so I am not going to invent a theory about it.
What can I control? I can answer carefully. I can keep the records organized. I can communicate with the people affected. I can keep working on the things that still move. And I can try not to let uncertainty make me careless with the people around me.
Every book needs more than one kind of chapter
A friend once told me that life is like a book. A book has many chapters, and not every chapter feels good while we are inside it. Some chapters are fun. Some are exciting. Some test our strength.
The difficult chapters are still part of the story.
I am trying to remember that now. There is pressure, there is uncertainty, and there is a lot to carry into Q4. There is also time with Miles, a team learning new ways to work, a Summit getting closer, and a chance to build useful things for the next layer of the internet.
Life is short, and life is a journey. I am grateful to be in this chapter, even if I would like a few pages to move faster.
What chapter are you in right now, and what is the other rail you need to stop neglecting?
Comments