SellerChat / ProdayChat / VendeChat
One product under three brands, one per market.
Built and developed by me, with AI coding agents.
Each one lands at a different level of involvement. That is the whole basis of how this is priced.
You have a working product and no idea which parts are solid. I read what exists, tell you plainly what you own, and we decide together what to do first.
Founder Technical Advisor
Someone proposes a rewrite, a new framework or a migration. You get a second opinion from a person with no stake in the answer, before you approve the invoice.
Founder Technical Advisor
Work gets broken down, prioritized and written with acceptance criteria. I set the tasks and I check what comes back against them.
Technical Development Lead
Architectural decisions get made once, written down and applied. Drift and half-finished work get named while they are still cheap to fix.
Technical Development Lead
I build it: the solution design, the code, the servers, CI/CD, staging and production. Short sprints, each one ending in something that works.
Vibe Coding
The same person, the same experience, three different amounts of responsibility. You can move between them.
I advise you, the owner, in writing. Technical questions, second opinions, briefs and prompts for Claude Code or Codex. Up to two hours a week on your project. I do not touch servers or code.
I run the technical work of your team: backlog, tasks, acceptance criteria, architectural decisions, review of what gets delivered. Your people build it, I make sure the right thing gets built.
I build the product myself with Claude Code Max and Codex Pro: design, implementation, servers, CI/CD, staging, production and the documentation that goes with it.
No discovery call to book and no sales sequence. You describe the product, I read it, and we start.
What it does, what it is built with, who works on it, what you are worried about. In your own words, in writing.
Advice, technical leadership or hands-on development. If you pick the wrong one, you move.
Your stack, your infrastructure, your team, what was already decided and why. This is what makes the second month better than the first.
Decisions, tasks and sprint results are written down, so a month later you can see what was done and why.
Describe your product and the problem in your own words, and pick the level of involvement that matches it. You can change it later.