Decide what to build, before anyone writes code.
Discovery, architecture, AI readiness, and UI/UX design. You leave with a scope you can defend, a design your users have already tried, and a roadmap your team can act on.
01The engagement
Every phase ends with something you keep.
You see what each step produces before the next one starts, and you can stop at any milestone.
- 1.1
Discover
Interviews and workshops with owners, users, and IT. We learn how the work really runs, not how the manual says it does.
You keepFindings, process maps, and constraints
You can stop here and keep what this phase produced. - 1.2
Define
We agree the outcome, the one metric that proves it, and the risk level of each step.
You keepProduct brief and success metric
You can stop here and keep what this phase produced. - 1.3
Shape
Architecture options and user flows, weighed on cost, risk, and time to value.
You keepRecommended architecture and flows
You can stop here and keep what this phase produced. - 1.4
Prototype & test
Clickable prototypes in front of real users. What confuses them changes before it costs a sprint.
You keepTested prototype and usability findings
You can stop here and keep what this phase produced. - 1.5
Hand over
A roadmap, estimate, and design system your team, or ours, can build from.
You keepRoadmap, estimate, and design system
02Scope
What we deliver.
Decide what to build, and how it should work for the people using it, before anyone writes code.
Call us when
- You know the problem, but not yet the scope or the budget.
- A system exists, but people work around it in spreadsheets and chat.
- You’re preparing for AI and don’t know which workflow to start with.
- You need an estimate and architecture you can defend to a board.
- 2.1
Business & Technical Consultancy
Discovery, architecture, AI readiness, and a roadmap your team can act on.
- Discovery workshops with the people who do the work
- Current and target process maps
- AI readiness and risk assessment
- Architecture options, with cost and trade‑offs
- A phased roadmap and estimate
- 2.2
UI/UX Design
Research, flows, prototypes, and design systems that make complex work feel simple.
- User interviews and usability tests
- User flows and information architecture
- Clickable prototypes, tested with real users
- A design system of tokens and components, ready in code
03Fees
Quoted before the work starts.
Solutions are project work: quoted after the free assessment, and billed apart from any product subscription.
- 3.1
Business & Technical Consultancy
Fixed fee
A fixed-scope discovery or architecture review, priced up front. You keep the roadmap whether or not we build it.
- 3.2
UI/UX Design
Fixed fee per phase
Research, prototype, and design system are quoted as separate phases, so you can stop after any one of them.
04Tools
Tools we run in our own products.
The same stack behind Batayan, ariarian.ai, and Habi. We pick per project, and work with yours where it already exists.
- 4.1
Discovery
Methods that surface how work actually runs, and what it costs.
Stakeholder interviews, Process mapping, Risk register, One‑metric definition
- 4.2
Research & testing
Decisions made with users, not about them.
User interviews, Usability testing, Clickable prototypes
- 4.3
Design systems
Built in code from day one, so the design and the product never drift apart.
Tailwind CSS tokens, shadcn/ui, Base UI, Reka UI
- 4.4
Accessibility
Checked while we design, not patched after launch.
WCAG 2.2 AA, Automated contrast checks, Keyboard and screen‑reader passes
- 4.5
Documentation
Written down where the team works, so decisions outlive the meeting.
Product brief, Design spec, Architecture decisions
05Standards
What doesn’t change from project to project.
- 5.1
Tested with users before build
Every major flow is tried by the people who’ll use it before engineering starts.
- 5.2
Accessible by default
Contrast, keyboard use, and screen readers are part of the design review, not a later audit.
- 5.3
You keep the work
The roadmap, research, and design system are yours, whether or not we build what comes next.
- 5.4
Design and engineering together
Engineers join discovery, so what we design is what can be built, on time and on budget.
06Questions
Strategy & design, answered.
How is this different from the free assessment?
The free assessment looks at one workflow. Consultancy is a fixed‑fee discovery across several workflows or a whole product, and ends in an architecture, a governance model, and a roadmap.
Do we have to build with you afterwards?
No. You keep the roadmap, research, and designs either way. Many clients build with us; some hand the work to their own team.
Can you design for a system that already exists?
Yes. We start from how people use it today, find where they work around it, and redesign those flows first.
Can we stop after one phase?
Yes. Research, prototype, and design system are quoted as separate phases, so you can pause after any one of them.
The rest of how we work.
- AI & automationSoftware that does routine work and escalates the rest, with an owner, a risk level, and an escalation path from day one.
- Build & qualityWeb, mobile, and commerce systems, tested before they ship and easy to keep running after.
- Staff AugmentationVetted engineers, designers, and QA specialists who join your team and work to your process.
- Working with LGUsDigital services for provinces, cities, and municipalities, procured your way and deployed for your LGU, with an accountable office owner for every step.
Your people stop doing the routine work. They still make the calls that matter, and they can always step in.
Tell us about one workflow that eats time or carries risk. We’ll reply with what software could handle, what it should hand to a person, and who stays accountable.