Fixed fee · 10 working days · Led personally by the founder
From a better website to the tools behind it, Spanwork helps you design, build, and maintain what your business needs.
01 / Websites and ecommerce
Business websites, online stores, and improvements to an existing site, shaped around your customers and the way you work.
02 / Custom apps and integrations
Customer portals, internal tools, and connected systems that give a recurring business process a practical home.
03 / Scoped ongoing care
Maintenance, fixes, and planned improvements for the website or software your business depends on. We agree on the systems, priorities, and support window first.
Already know what you need? We can scope the build directly. If the next step is unclear, a focused assessment can help you decide.
Discuss your projectSelected work from Jose's public portfolio. The relationship and role are shown for each example.
Related-business work / Service website
A service-business website connecting clear service information, estimate requests, and the owner's follow-up workflow.
Product portfolio / Publishing application
A publishing product with a profile editor, connected data, publishing controls, analytics, and billing.
Current operating role / Active beta
Product and platform leadership for a social gaming product, spanning UX, architecture, infrastructure, and operational reliability.
Optional discovery / Illustrative sample
A focused assessment can clarify the scope before you commit to a build. For a consequential product or platform decision, the Product and Technology Review is available as a standalone engagement.
Optional discovery / The Product and Technology Review
For one expensive product or platform decision, get a recommendation, the reasoning behind it, and a practical 90-day plan in 10 working days. Start here when the direction needs investigation; start with a project scope when it is already clear.
An illustrative sample, not client work. Your Review is scoped around your decision.
You keep the recommendation and plan. No follow-on engagement required.
Should the team begin a full platform rewrite before committing to enterprise identity and audit controls?
Separate identity and audit responsibilities, test the integration boundary, and measure one release cycle before approving the larger program.
Enterprise identity controls and a reliable audit trail before launch.
Identity and audit responsibilities share an untested boundary.
Name the leader responsible for the decision and the team that will operate it.
What could change the answer? Test failure, rollback, and data behavior before the next commitment.
Name the owners. Document the boundaries. Agree on the test.
Run the smallest complete test. Observe one representative release.
Compare the findings. Choose the next scope, owners, and accepted risks.
Leadership readoutApprove / Narrow / Defer / Stop
We agree on the outcome and scope, build in reviewable stages, and prepare you to run what we deliver.
Talk through the customers, workflow, existing systems, and what needs to change.
Set the deliverables, responsibilities, timeline, and fee in writing. Use discovery only where an important unknown needs investigation.
Review working progress, test the important flows, and agree on changes before they expand the scope.
Check the agreed scope, document how to manage it, and plan any ongoing care as a separate agreement.
Jose Alvarado is your direct point of contact for scope, design, development, and handover.
Founder, Spanwork Product and platform engineer
Jose is the founder of Spanwork and CTO at Micr. He leads product direction, UX, architecture, and infrastructure for an active software product.
His published work includes service-business websites, publishing tools, and social gaming. He connects product design with full-stack development and the systems needed to keep software running.
Read how to choose between repair and rewrite, test an enterprise promise, and get stalled roadmap work moving.
A new build, an improvement to an existing system, and ongoing care each need their own scope. You can engage Spanwork directly for the work you need.
Before work starts
Agree on deliverables, timeline, fee, access needs, and who supplies content or approvals. Additional requests are discussed before they become additional work.
Ongoing support
Agree on the systems covered, maintenance tasks, support hours, and improvement priorities. Ongoing care is scoped separately from the initial build.
Share the business need, your current website or tools, and any timing constraints. A few sentences are enough to start a project conversation.
A short summary is enough. Do not send confidential code, credentials, customer data, or system access through this form.
If there is a fit, the next step is a short conversation. You receive the scope, timeline, deliverables, access requirements, and fixed fee in writing before deciding.
hello@spanwork.net Use the protected inquiry
