Partner
Bring the problem
Three kinds of people should write. Someone with an idea who needs a technical partner part of the time. An investor who wants a read from someone who has run the operation, not just the model. And someone looking for a co-founder who builds.
This is a filter rather than a services page. What follows is who it tends to work for, what I look for, and what to send so we both find out quickly whether it fits. There is no form and no call booking link. An email does the job better, because what you write in it is most of the answer.
Who
Who should write
You have the idea and not the technical half
You know the problem, you may already know the market, and you do not have someone who can build it and tell you the truth about it at the same time. Fractional means a defined piece: the architecture, the first working version, or the decision about what to buy instead of build. Not a full-time seat, and not a body shop either.
You are an investor with a question
Usually it is whether the thing is buildable at the cost claimed, or whether the operation behind it survives contact with real volume. I have written the capital case and I have stood on the floor it was written about. That is a different read from a technical diligence, and the two do not substitute for each other.
You want a co-founder who builds
Rarer, slower, and worth saying out loud anyway. Two businesses started and sold, three products shipped and running, and a fourth built and handed to a client who runs it now. If you are looking for someone to own the building half, that is a conversation worth having properly.
Fit
What fits, and what does not
Said plainly, because a mismatch found now costs an email and a mismatch found later costs a quarter.
You will write down what would make you stop
The strongest single signal. A condition set before the first result is a threshold. The same condition set afterwards is a negotiation, and you will lose it to yourself. There is a case study on this site about an experiment that fired every one of its kill conditions, which is what the discipline looks like when the answer is no.
The problem is real before the product is
I will ask what breaks today, who it breaks for, and what they do instead right now. Every idea worth building has an answer to that already happening somewhere, usually badly and in a spreadsheet. If there is no answer yet, the honest next step is not to build.
There is an operation, not only an app
What I know is what happens when software meets a shift, a building, a truck or a regulator. If the problem is purely a consumer app, someone else is a better fit and I will say so rather than take the work.
Buying beats building until it does not
The first question is always what can be bought, because building everything is slow and expensive. I build the gap, not the whole thing. If you want everything built from scratch, I am the wrong person and it will show early.
What to send
Four answers
No form, no application portal. Write an email that answers four things.
One
What breaks today, and for whom.
Two
What those people do instead, right now, while it is broken.
Three
What you have already tried, including what you have bought.
Four
What result would make you stop.
Three paragraphs is plenty. A deck is welcome but the four answers matter more, and the fourth one matters most. If it fits I will say so. If it does not I will say that and why, because a fast no is worth more to you than a slow maybe.
Contact