Contact
How to reach us
There are two ways to work with SSOAC. Each has a dedicated address and a short list of what helps us respond well. We read what comes in and reply with a real conversation about the work.
Two ways to engage
Most people who reach out want one of two things: software built for their own work, or a place in a product as a founding cofounder. We keep these on separate addresses so your message lands with the right context from the start. If you are unsure which fits, write to either one and describe your situation; we will point you the right way.
Have software built (clients)
Write to build@ssoac.com. This is for anyone who needs a tool for their own operation — a workflow, a record system, a small internal application — and wants SSOAC to design and build it.
Join a product (cofounders)
Write to cofounders@ssoac.com. This is for people who want to help a piece of software reach the people who need it, give feedback that shapes it, and share in its sales under the cofounder model.
Writing to us about custom software
A first message to build@ssoac.com does not need to be a formal specification. We would rather understand the work you do than read a feature list. The items below help us respond with something useful rather than a generic reply; none of them are required to start.
What you do
The activity or business the software is meant to serve, in plain terms.
What you are trying to fix
The task, process, or friction you want handled differently — what is slow, manual, or error-prone today.
Who would use it
Roughly how many people, with what level of comfort using software.
Any constraints
Tools you already rely on, a rough timeframe, or anything the software must or must not do.
Writing to us about the cofounder program
A first message to cofounders@ssoac.com is the start of a conversation, not an application to be scored. We are early, and founding seats are open. Tell us where you can genuinely help a product find its users. The cofounder model and its terms are set out in full on the operating terms page; the points below are simply what makes a first exchange productive.
Where you have reach
The activity, industry, or audience you know well and could introduce a product to.
How you would help
Distribution, feedback, domain knowledge — what you would actually contribute to a software's growth.
What interests you
If a current or planned product already fits your world, say which and why.
What happens next
After you write, we reply to talk about the work — not to move you through a sales script. We will ask questions, share what we can and cannot reasonably do, and be honest if SSOAC is not the right fit for what you need. We are an early company building our first software, so we describe where things actually stand rather than promise more than we can deliver. If a custom build or a cofounder seat makes sense, we agree on the shape of it together before any work begins.
A conversation first
We start by understanding the work, then discuss what is realistic. No commitment is asked for at this stage.
Straight answers
If something is outside what we can do well right now, we say so. We would rather decline than overpromise.
Clear terms before work
If we proceed, the scope, the arrangement, and the operating terms are agreed before anything is built.
Before you write
A few things are worth knowing up front so there are no surprises. SSOAC holds the licenses to produce its software but is not liable for damage arising from its use. We provide support and adapt software to your needs, but we do not guarantee that support is available at all times or that products are maintained continuously. Digital products are not refundable, except at our discretion. These terms are stated in full on the operating terms page, and we are glad to walk through any of them with you.
Where to write
For custom software, write to build@ssoac.com. To join a product as a cofounder, write to cofounders@ssoac.com. Tell us about the work, and we will take it from there.