You see it running in week two
Most software projects go quiet for three months and then show you something. Ours does not. Because the platform underneath is already built, we can put your business on real software in days — so you spend the project correcting something you can click, instead of imagining something you cannot.
The four stages, with real durations attached
Week one
We sit with you
We spend real time watching how your business actually runs — not how an org chart says it runs. The spreadsheet somebody rebuilt three times. The five apps that do not talk to each other. The thing one person does by hand every Friday afternoon that nobody else knows how to do.
You do not need to prepare anything or write a requirements document. If you can walk us through a normal week, that is enough.
What you get: a written map of how your business works today, and a plain list of what is costing you time.
Week two
You see it running
Not a slide deck and not a picture of a screen. Your business, on working software, with your own products and customers and prices in it, on a real address you can open on your phone and hand to somebody else.
This is the point of owning the platform. Eighty percent of what any business needs already exists and already works, so week two is a configuration job rather than a construction job.
What you get: a live system you can click through, and an honest list of what is still missing.
Weeks three to six
We build your part
The twenty percent nobody else does the way you do it — your pricing rules, your approval chain, the report your biggest customer insists on, the machine on your floor that needs to be talked to.
You see the work every week and you tell us when it is wrong. Correcting something in week four is ordinary. Discovering it in month six is expensive, which is why we do not work that way.
What you get: the parts that are genuinely yours, built and running, reviewed weekly.
After that
We keep it running
We host it, watch it, back it up, and stay on call. When something breaks at four on a Friday, you call us and a person answers — you do not open a ticket and wait.
It does not get handed over and forgotten. The platform keeps improving underneath you, and you get those improvements without paying for a rebuild.
What you get: hosting, monitoring, backups, and a phone number that works.
How we behave while we do it
We talk like people
You will never be handed a document you need a technical background to read. If we cannot explain something in plain words, we do not understand it well enough yet.
You talk to the builder
There is no account manager relaying messages to a team you never meet. The person who writes your software is the person you talk to about it.
We say no
If what you need already exists for forty dollars a month, we will tell you to go buy it. We would rather lose the project than sell you something you did not need.
Nothing goes quiet
You see working software every week from week two onward. If a week goes by without something to show you, we tell you why before you have to ask.
It is your business, not ours
We do not reshape how you work to suit the software. That is the deal everywhere else, and it is the reason you are reading this page.
Your data is yours
You can take it out whenever you want, in a format other software can read. We do not hold your information hostage to keep your business.
What we need from you
Less than you think. This is the whole list.
A few hours in week one
Enough time to walk us through a normal week, and permission to ask the people doing the work how they actually do it.
One person who can decide
Somebody who can say yes or no without convening a committee. Projects stall on decisions, not on code.
Your real information
Your actual products, prices, and customers — however messy the spreadsheet is. We would rather clean up real data than build against invented data that behaves too well.
An hour most weeks
To look at what we built and tell us what is wrong. Blunt is useful. Polite is expensive.
Questions people ask before they start
How long does the whole thing take?
Most businesses are running on something real within six weeks. Simple setups are live sooner; operations with a lot of custom rules take longer. We will give you a range after week one, once we have seen the work rather than guessed at it.
Do we have to stop using what we have now?
Not on day one. We usually run the new system alongside the old one until you trust it, then switch. Nobody should be asked to bet their week on software they have used for four days.
What if we change our minds halfway through?
That is expected, and it is why you see working software every week. Changing direction in week three costs a conversation. The only expensive version is the one nobody mentions until the end.
What happens if we want to leave?
You take your information with you, in a format other software can read, and we help you move it. No exit fee and no hostage-taking. A business that stays because leaving is painful is not a business we want.
Are we too small for this?
Almost certainly not. A two-person shop and a forty-truck distributor need the same things underneath — a website people can find, a way to get paid, and records that stay straight. The difference is how much of it you turn on.
Do we need somebody technical on our side?
No. Most of the businesses we work with have nobody in an IT role and no intention of hiring one. That is the normal case, not the exception, and it is why we stay on call afterwards.
Start with a conversation, not a contract.
Tell us what is broken in your own words. We will tell you what it would take to fix it and roughly what it would cost — and if we are not the right people, we will say so and point you somewhere better.
Tell us what's brokenOr email hello@wize.works — a person reads it, usually the same day.