Software
The website. The application. The tools to run it.
We build complete software products: the public website, customer experience, product features and owner dashboard, with frontend and backend deployment and a clear handover.
The engagement
Complete Product Build
The public website, customer application and admin tools, built and deployed together.
For founders, product teams and businesses commissioning B2B or B2C software, a custom application, or a replacement for a workflow that no longer fits.
Bring the product idea or existing workflow. We will define the first release, its boundaries and how you will review it.
What you receive
- A branded marketing website with the agreed product and resource pages
- Accounts, onboarding and the core customer workflows
- Admin tools, data storage, email and required API connections
- Frontend and backend deployment, code and data handover
We agree the deliverables, timeline and project price in writing before work begins.
Explore the work.
Published projects you can inspect. Each case study links to the product itself.
Govern
View project →A trust layer for autonomous software, giving AI agents verified identities, scoped permissions, spending limits and signed action receipts.
Tellme
View project →An alternative to static forms that interviews people and turns their answers into a complete, structured record.
The scope, in detail.
Build the complete system or bring us a specific part. We agree the deliverables around your project requirements.
The public product website
Branded marketing pages for the product, solutions, resources, blog, About, Contact and approved legal content. Genuine testimonials and relevant calls to action connect the website to the application.
Accounts and customer experience
Custom account setup, onboarding, the product dashboard, profile and settings. We design the customer journey around the product's actual features, roles and data.
The application itself
Booking systems, CRMs, social and community platforms, B2B and B2C applications, internal tools and Web3 products. We agree the product-specific capabilities and acceptance scenarios before development.
The owner's dashboard
Authorized user management, refund operations, financial visibility and other agreed administrative tools. Roles and access are enforced around the operations each person is allowed to perform.
Data and integrations
Custom databases, third-party data APIs, email, custom APIs and MCP interfaces where needed. Data ownership, vendor dependencies and operating costs are documented.
Deployment and ownership
Frontend and backend deployment assistance, source code, configuration guidance and a practical handover. Your accounts and data remain yours. Payment milestones, commissioned IP transfer and third-party licenses are stated in the agreement.
Ways to work together.
The complete engagement and the focused options below use the same approach: agree the result, build it, review it and hand it over.
Complete software product
The public site, customer application, admin tools, integrations and deployment in one scoped engagement.
One working business workflow
A focused implementation connecting a specific task and its systems.
Product prototype
A representative vertical slice to test a product decision before a larger build.
Booking systems
Scheduling, availability and the booking exceptions your business needs.
CRM build or extension
Customer records, workflows and integrations around your operating process.
Social and community products
A scoped pilot or complete product with accounts, interactions and moderation requirements.
Web3 implementation
Begin with a bounded integration or prototype; production transactions require additional security and operational scope.
Custom API
A documented interface connecting your product, data and other systems.
From the brief to the handover.
- 01
Define the users, business model, permissions and required product journeys.
- 02
Review the brand, architecture, interface and representative working slice.
- 03
Build and test customer, admin and integration behavior.
- 04
Deploy the frontend and backend, transfer the agreed assets and document operations.
How we review the result
- A customer can sign up and complete the agreed core journey.
- Authorized owners can manage the agreed users, transactions and operations.
- Data persists correctly and the frontend, backend and integrations work together.
What shapes the proposal
- Core workflows and user roles
- Integrations and data migration
- Admin, payment and deployment requirements
Price and timing follow the agreed scope. Third-party subscriptions and optional ongoing support are listed separately.
What we need to begin
Product goals, priority features, user roles, existing data, provider accounts, approved business content and an owner for acceptance decisions.
Scope boundaries
Feature scope, integrations, data volumes and acceptance tests determine the project. A prototype is not a complete production product. Hosting, vendor usage and optional retainers are separate; ownership does not require an ongoing retainer.
Service deck · PDF
Take the details to your team.
The scope, deliverables, delivery and handover in one document. Read it here or download it without submitting your email.
Read the pitch →Before we begin.
A few practical questions about software.
You own the project code, deployment and data under the agreed terms. We provide the handover and deployment assistance. Third-party services retain their own licensing terms; an ongoing retainer is optional.
Before you begin · From the blog
Custom software vs SaaS: how to decide for a small business
Compare custom software and off-the-shelf SaaS using workflow fit, ownership, integration costs and a practical decision checklist.
Read the guide →Tell us what you
want to build.
Bring your current site or product, what needs to change, and your target date. We will put the proposed scope, milestones and price in writing.