Tell us what you're building.
Whether it's an AI feature, a customer-facing agent, a SaaS MVP or a site that needs to rank, start here. Every inquiry is read by the founder.
Project inquiry
A few sentences is enough. The most useful things to tell us are the problem, who has it, and where you are today: idea, prototype or live product.
Prefer email?
Write to cyphorux@gmail.com. You can also reach the founder on LinkedIn or X.
A good first message
An illustrative example of the detail that lets us reply with useful questions instead of generic ones:
We run a 12-person HVAC company. Technicians send job notes by text, and our office manager spends two mornings a week turning them into quotes. We want a tool that drafts the quote from the notes and our price list, with a human approving before it goes out. We have a spreadsheet of past quotes we can share. We'd like something in use before the summer season.
Helpful to include
- The workflow or problem, described the way your customers would describe it.
- Who your first customers are, and how you'll reach them.
- Anything that already exists: a prototype, a spreadsheet, a live product or a codebase.
- Hard constraints, such as a launch date, a compliance requirement or an existing stack.
- Examples of the inputs an AI feature would handle, if you can share them.
After you hit send.
- 01
You get a written reply
Usually within two business days, from the founder. It will include questions about the problem, the people who have it, and what success looks like, not a generic sales deck.
- 02
A short call, if it's a fit
We walk through the workflow together and look at any real examples you can share. If it isn't a fit, we'll say so and, where we can, suggest what to do instead.
- 03
A written scope and a fixed price
We send a scope document with what we will build, what we won't, the timeline, and a price agreed against that document.
- 04
Kickoff
Accounts are set up in your name, the spec is finalized, and the first preview deployment goes live in week one.
Useful reading.
- Our process, phase by phase
How a project runs from written spec to production.
- Services overview
AI products, LangGraph agents, SaaS MVPs and Next.js web development.
- Case studies
ScopeCrafters and ContentVo: what we built, how, and what we cut.
- About the founder
Track record, principles and why Cyphorux builds its own products.
Before you reach out.
Pick "Not sure yet". Budget depends on scope, and scope is what the first conversation is for. Once we understand the workflow, we'll give you a range and show you which cuts would bring it down.
Yes. Keep the first message high level if you prefer, and ask for a mutual NDA before sharing details. We're happy to sign one before the scoping call.
Yes. Projects run async-first: written weekly updates, a preview URL that's always current, and one shared channel, with calls scheduled in overlapping hours.
We'll tell you. If the problem needs a different kind of team, or doesn't need custom software at all, saying so early saves both of us time.
See what we do and don't build