Solutions / custom software
A few clients a quarter. On purpose.
NexaSphere is a product company first. Most of the week goes into our own products. The rest goes into a small amount of paid client work, because building the thing an operator actually needs is the fastest honest way to find out what is worth turning into a product.
That is the whole arrangement. You get software that ships. We get a real problem to learn from.
- Capacity
- A few clients a quarter
- First slice
- Fixed scope, fixed price, a date
- Ownership
- The code and accounts are yours
- Reply
- Two business days, including the no
Photo: Ian Findley, Pexels
01What we take on
Three shapes of work, each one we do for ourselves.
If yours is close to one of them, the conversation will be short and useful. Beside each one is our own work you can open and check, because there are no client stories to show yet.
Ship an iOS app
You have a workflow your team already does on paper or in a spreadsheet, and it belongs on a phone. We scope it, build it in Swift and SwiftUI, and take it through App Store review.
Build the internal tool
The web app nobody has time to build: intake forms, reporting, an operations dashboard, a data pipeline that stops being a person copying rows between tabs.
Get found in AI search
Technical audit and content work for teams who noticed their traffic move from Google results to ChatGPT and Perplexity answers, and want to be cited in them.
02 The standard
Done means walked, not compiled.
This is how our own software is checked. Bill-ready, still in development, was walked screen by screen on synthetic data, from an empty queue to an invoiced load. Its page was rewritten the same day to claim only what that build does.
The screen on the right is from that walk. It is the product, not a mock-up.
03Who this is for
Being specific here saves us both a call.
Good fit
- You are the person who can decide, and you are in the room
- The problem is one you already have, not one you are guessing at
- A first working version can land in weeks, not quarters
- You want the code and the accounts to be yours at the end
Not a fit
- Staff augmentation, or a seat on someone else’s sprint board
- Rescuing a large codebase we did not write
- Equity instead of invoices
- Work that needs a team, an on-call rotation, or a compliance program
04How it works
Four steps, and you can stop after any of them.
You write in
One message describing the problem, who has it, and what happens today when nobody solves it. No form with eleven fields.
We reply either way
If it is not a fit, you get a straight answer and, where we can, a pointer to someone better suited. If it is, we book a call.
A scoped first slice
Fixed scope, fixed price, a date. Small enough that you can judge the work before committing to more.
Then a retainer, or not
If the first slice went well, we continue on a monthly retainer. If it did not, you own everything built so far and we part cleanly.
On pricePricing depends entirely on scope, so there is no rate card on this page. We quote a number before any work starts, and it does not move unless you change what you asked for.
05 Inquire
Tell us the problem, not the solution.
Use the contact form, or email [email protected]. Either way, the three things worth including:
- 01The problem, and who in your org runs into it.
- 02What you do about it today, even if the answer is nothing.
- 03Roughly when you need something working.
We read every inquiry and reply within two business days, including the no. Availability is limited, so there are stretches where the answer is not yet.