SaaS founder · @alexkravchenko
Alex Kravchenko
Founder background
In search of product-market fit. I build things and look for their users.
Expertise
- Engineering
Products
WPMissionControl
AI-powered monitoring and early-warning insights for WordPress websites.
TomorrowGone
Share a one-time secret that disappears after the first successful reveal or after 24 hours.
SomedayCertain
Simple Calendar Scheduling
OnceRevealed
Timed interviews that preserve a respondent’s first answer before reconsideration.
TodayMet
One profile for different conversations
Recent posts
TodayMet now has a public GitHub repository
We’ve published the first version of TodayMet’s public developer repository. It brings together the resources developers and AI agents need to understand and integrate with TodayMet: - API documentation and practical examples - Model Context Protocol (MCP) setup and tool reference - Profile and content-model documentation - Examples for links, documents, galleries, maps, media, and testimonials - Privacy, visibility, and responsible-integration guidance - MIT-licensed code examples and CC-licensed documentation TodayMet helps people and organizations create structured, shareable professional profiles that can be maintained directly or with the assistance of compatible AI tools. The public repository makes that integration surface easier to inspect, test, and build upon. This is an initial public release, and we’ll continue updating it as the platform evolves. Repository: https://github.com/TodayMet/todaymet Product: https://todaymet.com Feedback, issues, and integration ideas are welcome.
We’ve expanded TodayMet’s example profile library from 8 to…
The 15 new profiles cover professions including graphic design, illustration, video editing, voice acting, translation, virtual assistance, interior design, architecture, consulting, academic research, writing, journalism, public speaking, acting, and music. These aren’t just placeholder pages. Each profile demonstrates how TodayMet can work for that profession, including: - Profession-specific introductions, highlights, and calls to action - Protected contact details such as personal email, WhatsApp, and LinkedIn - Protected résumés and selected private materials - Location and Google Maps integration - “Currently” and “Working style” sections - Realistic content structure and visual presentation - A dedicated guide explaining how to build an effective profile for that use case The profiles and guides link to each other through a central examples hub, giving visitors a clearer path from researching a use case to seeing the finished result. We also updated the sitemap workflow so editor-managed profiles are automatically exposed to search engines after creation, without requiring another application build. All 30 new profile and guide URLs have now been submitted through Google Search Console. Explore the full library: https://todaymet.com/examples
TodayMet update: access requests now trigger email…
Another small but important piece of TodayMet is now live: email notifications for protected information requests. Until now, TodayMet already allowed visitors to request access to protected information on someone's profile. The profile owner could review the request and decide what to share. But there was an obvious gap: how would the owner know someone had requested access? They would have to return to TodayMet and check manually. That's not a particularly realistic expectation for a profile someone might create once and share occasionally. So I finally connected the missing piece. I configured Resend for transactional email delivery, along with a server-side cron job that retries notifications when delivery fails. Now, when someone requests access to protected items, the profile owner receives an email containing: - Who requested access - Which protected items they requested - Their accompanying message - A direct link to review the request Importantly, nothing is shared automatically. The owner still decides which information to reveal and how long access should last. This matters because selective sharing is one of TodayMet's central ideas. A public profile can introduce you to someone, but not everything belongs on the public internet. Your résumé, private contact details, documents, or other information might be appropriate for one person and not another. The request-and-approval flow makes that possible. Email notifications make it practical without requiring people to keep checking the app. There's also a small engineering lesson here. Sending an email is easy. Making sure a notification isn't simply lost when something temporarily fails requires a little more thought. Hence the retry mechanism. Nothing particularly sophisticated, just a boring piece of reliability infrastructure that belongs in the workflow. I'm increasingly finding that building TodayMet isn't about adding more impressive features. It's about making the existing interactions complete enough that someone can actually rely on them. A visitor requests access → the owner gets notified → reviews the request → decides what to share. One more loop closed. Still early, still small numbers, and still plenty to learn from real users. But TodayMet is gradually becoming less of a collection of capabilities and more of a product that works end to end. https://todaymet.com
Benefit first, signup later
Today I tried a small acquisition experiment with TodayMet. Instead of DMing people and asking them to sign up, create a profile, fill in their information, and hopefully discover the value... I did the work first. I researched a few founders and their products, used my Codex MCP integration to build complete profiles for them, then sent each person a private claimable preview. No signup required. If they didn't like it, they could simply ignore the link and the draft would disappear. The response was surprisingly good. Profiles were claimed and published, one person shared his publicly, and another signed up and started exploring the paid features without me asking. Her description of the experience was better than mine: “Benefit first, then I found the upgraded version.” That might be the lesson. Sometimes the onboarding problem isn't that your onboarding has too many steps. Maybe the problem is that you're asking the user to do the work before they've experienced the benefit. I'm going to keep testing this.
Two users asked the same question
A small TodayMet activation lesson this week. Publishing a profile seemed completely obvious to me. At the top of the editor there's a status control: Draft → Published → Paused I built it, so naturally I knew exactly what it meant. Then one user created a profile and asked how to publish it. I noticed the problem, but initially thought clearer guidance around the status control would probably be enough. Then a second user independently went through the same flow and asked: “How do I publish?” At that point it stopped being an isolated confusion and became a UX problem. The fix was deliberately small. The status dropdown stays because it makes sense for ongoing profile management. But while a profile is still a draft, the editor now shows an explicit activation step: Your profile is ready to share. Publish it to make your public profile available. Publish profile → Once published, that prompt disappears and the normal sharing controls take over. No onboarding wizard. No tutorial explaining where the dropdown is. Just make the thing the user needs to do next obvious. The useful lesson for me is how easy it is to become blind to your own interface. I know TodayMet's state model. I know why something says Draft. I know which control changes it. So my brain fills in all the missing information automatically. A new user doesn't have any of that context. And this is another reason I'm increasingly interested in getting more people through the product rather than polishing it alone: one confused user can be an accident. two independently confused at the same step is a signal. Fix it, send more people through, and see if the question disappears.
Did you know, fellow founders, that my app TodayMet offers a…
The only thing you need is to navigate to todaymet.com and create your own profile OR a profile of your company/product - you can choose a Person or an Organization. This way you'll get a backlink, and an indexable page with relevant Schema.org markup. Another brick in your foundation! An example profile is shown on the attached screenshot. Or, if you don't have time, there is an even simpler solution: I have my local concierge MCP that allows me to establish a new profile in minutes! Just reach out to me, drop your assets, and I'll get things sorted for you. Then you'll just need to claim your profile and be done with it! The submission is completely free, unless you decide in future to make a more rich profile with additional widgets and hosted files, which probably won't be needed anyway. Happy to have all of you on board and expand your internet presence!
Small traffic is already finding real problems
Another external review of TodayMet came in, and this one was particularly useful because the reviewer actually tried to go through the funnel. There was some good news first: they found the concept interesting and said the landing page earned their attention. That's meaningful because several earlier reviewers had the opposite problem — they weren't sure what TodayMet actually did. I recently simplified the homepage around: One profile. Share what fits. and moved the public/private sharing model much higher up the page. This reviewer got past that problem. Then they clicked Create your profile, authenticated with Google, reached the first onboarding screen… and stopped. The first field asks you to choose your TodayMet address. The UI showed todaymet.com/ next to an input, but didn't clearly explain that the input expected only the final part of the address. So the reviewer reasonably entered something like: todaymet.com/claire The browser responded: Please match the requested format. And that was the end of the session. This is exactly the kind of early feedback I'm looking for. The problem wasn't that TodayMet needed another feature. A person was already interested enough to create an account, and an existing piece of UX prevented them from continuing. I've now updated the address step so the expected input is clear, validation gives useful feedback, and obvious inputs such as pasted TodayMet URLs can be handled rather than rejected with an obscure browser message. What I like about these first tiny bits of traffic is that the bottleneck seems to be moving. First: “I don't understand what this product does.” So I simplified the homepage. Now: “I understand it, tried to create a profile, and got stuck here.” So I fixed onboarding. That's a much more useful development process than trying to imagine the next ten features in advance. The numbers are still tiny. But the loop is alive: traffic → attempt → friction → feedback → fix → more traffic For now, I want to keep feeding that loop.
TodayMet homepage: less explaining, more showing
A useful pattern started appearing in the first feedback on TodayMet. The design was generally received well, but several people had trouble understanding the product quickly enough. One person even explored the example, signed up, created a profile — and still wasn't entirely sure what TodayMet was for. That was a pretty good signal. The old homepage wasn't necessarily missing an explanation. If anything, it had too many explanations of the same idea. “Be easy to remember.” “One profile. Different conversations.” Several use cases. Public / protected / hidden information. Individually they made sense, but together they left too much interpretation to the visitor. So I've simplified the story around one much more literal proposition: One profile. Share what fits. And immediately after that: Public for everyone. Private when it matters. The homepage now uses more of the actual product UI to explain what that means: public information, information shared after approval, private links, contact details, projects and profile elements. The use-case section was also rebuilt around small pieces of the product instead of mostly text. I also removed a large “how sharing works” illustration. It was good on its own, but after the changes it was explaining something the page had already explained twice. This is still a very small experiment. Traffic is a trickle, Search Console is only beginning to show activity, and the number of real profiles is small. But that's already enough to create something I didn't really have with some previous projects: traffic → feedback → change → more traffic For now, that's the loop I want to keep running. No grand redesign and no new feature backlog from a handful of comments. Just make the existing product easier to understand, then put it in front of more people and see what happens.
Small TodayMet update: profiles are no longer just for…
Products, startups and other organizations can have their own profiles too. I started by making TodayMet a TodayMet profile, because apparently recursion is a feature now. For builders, this also means you can create a profile for your product, add its website and other links, and get another public page pointing back to it. Here’s TodayMet eating its own dog food: https://todaymet.com/todaymetapp If you’re building something, feel free to make one for your product too.