WebsiteClient work
Maalica
A coaching website, offline event check-in, and one place to manage leads and payments.
Explore the websiteSaaS and custom business software
Build software around the way your business needs to work.
Outgrown spreadsheets? We build internal tools, customer portals and subscription software around your workflow.
Who it is for
Companies outgrowing spreadsheets and disconnected tools, founders planning a subscription product, and teams that need a customer portal or an internal system built around their own workflow.
What “SaaS” means
SaaS means software people use online, often through a subscription. You may need a SaaS product for customers, or a private tool for your own company. We help you choose the right starting point.
What we do
What the work includes, and what you receive.
| Work | What it means for you | What you receive |
|---|---|---|
| Workflow and product discovery | Understand users, tasks, current tools and constraints | A business and product brief |
| Release planning | Agree the smallest useful first version | A prioritised roadmap and acceptance criteria |
| Roles and permissions | Decide who can see and change each part | A user-role and access map |
| Experience design | Make complex work easier to follow | Flows, prototypes and interface designs |
| System planning | Work out how the product, data and integrations fit together | A technical plan explained in everyday terms |
| Application build | Implement the agreed workflows and screens | The working application and source access |
| Backend and data | Store and move information reliably | Agreed data model, APIs, validation and access controls |
| Product operations | Support the people managing the system | Admin tools and agreed audit, export or reporting features |
| Quality and deployment | Check key workflows and prepare the live environment | Test results, release process, monitoring and recovery plan |
| Handover and iteration | Keep the system understandable as it develops | Documentation, access inventory, training and next-release priorities |
How the work moves
Five steps you can follow.
Each step ends with something you can review. Read how we work.
- 01
Understand
Map the users, the tasks and the tools already in use.
- 02
Shape
Agree the first useful release, the roles and the acceptance criteria.
- 03
Build
Design the flows and build the application, data and integrations.
- 04
Check
Test the key workflows, permissions and errors before go-live.
- 05
Operate
Deploy, train the team and agree the next release.
What we clarify before promising a build
These become project-specific requirements. We do not describe every project as enterprise-grade by default.
- The expected users and usage pattern
- Sensitive data and who may see it
- Client or tenant separation
- Payment flows and subscriptions
- Availability needs
- Retention, deletion, backups and restore checks
- Who responds to incidents
- Migration quality and integrations that depend on other providers
Options to scope separately
- Customer onboarding
- Billing and subscriptions
- Separate workspaces for different companies
- Reports
- File management
- Data migration
- Third-party integrations
- Approval flows
- AI-assisted features
- Import and export
- Ongoing product improvement
Proof you can open
How we show software work
The Maalica event and sales platforms are custom software built around one team's real workflow: roles, check-in, payments, commissions and a live dashboard. Scription and Glip show the products we have shipped ourselves.
What good looks like
A person can complete the agreed job. Access rules behave as intended. Important errors are visible. The team knows how to operate, update and recover the system. The next release has a reason to exist.
Questions
Specific to saas & custom software.
Can we start with a smaller version?
Yes. We can define a useful first release and keep later ideas in a prioritised roadmap.
Can you replace our spreadsheets?
We first map the work those sheets perform. Sometimes a focused tool is useful; sometimes improving the existing setup is enough.
Do you take over an existing product?
We can begin with a code, design and operations review, then agree a realistic improvement plan.
What would you like your business to do better?
Tell us what you want to build or improve. A rough idea is enough.