Built with clarity.
Delivered with care.
Good collaboration should not be a black box. Here is how Anvilstead approaches planning, building, reviewing and handing over custom software.
Five steps.
Clear expectations.
This is a typical process, not a promise that every engagement has the same scope or timeline. Commercial terms are confirmed before work starts.
Explore the problem
We start with users, business objectives, current tools, timeline and constraints. Existing project files and sensitive credentials stay under the access terms agreed with the client.
Agree on what will be built
We turn assumptions into a written scope, including deliverables, risks, dependencies, review points and the boundaries of responsibility. We do not quote guaranteed results before understanding the system.
Work in visible increments
Implementation can include design systems, custom web or app development, integrations, AI agents and backend components. We aim to demonstrate working software at agreed stages.
Test the real paths
We review critical workflows, mobile usability, integration responses, error states and handoff needs in proportion to the contracted project scope. Visual fidelity matters, but reliability comes first.
Transfer with context
Deployment assistance, source delivery, documentation, configuration ownership and maintenance arrangements are made explicit in the agreement—not assumed.
Visible progress.
Documented decisions.
Each stage should produce something you can discuss, review or accept—not just another status update.
Explore the problem
We start with users, business objectives, current tools, timeline and constraints. Existing project files and sensitive credentials stay under the access terms agreed with the client.
Typical output: A shared problem statement and prioritized goals.
Agree on what will be built
We turn assumptions into a written scope, including deliverables, risks, dependencies, review points and the boundaries of responsibility. We do not quote guaranteed results before understanding the system.
Typical output: A reviewable proposal, milestones and acceptance criteria.
Work in visible increments
Implementation can include design systems, custom web or app development, integrations, AI agents and backend components. We aim to demonstrate working software at agreed stages.
Typical output: A working increment or milestone demonstration.
Test the real paths
We review critical workflows, mobile usability, integration responses, error states and handoff needs in proportion to the contracted project scope. Visual fidelity matters, but reliability comes first.
Typical output: A review log, tests and resolution of agreed issues.
Transfer with context
Deployment assistance, source delivery, documentation, configuration ownership and maintenance arrangements are made explicit in the agreement—not assumed.
Typical output: Agreed files, deployment notes and next steps.
See the kinds of engineering decisions these steps support in our documented work.
Explore selected projects ↗Before we
get started.
A few useful details about engagement, deliverables and the boundaries of our public portfolio.
Do I need a finished specification to contact you?
No. A concise description of the problem, users and desired outcome is enough to start. We can help turn it into an actionable scope before work begins.
Can you work with an existing codebase?
Yes, when the scope and access conditions make that practical. We begin with a review of the existing stack, dependencies, security boundaries and current behavior before proposing changes.
Do you provide both the interface and the backend?
Depending on scope, we can build end-to-end software including interfaces, APIs, data flows and operational integration. Specific deliverables are confirmed in writing.
How do milestone reviews work?
We agree on review checkpoints and acceptance criteria before implementation. The format and frequency vary with project size, dependencies and collaboration needs.
Will I receive the source code?
Source-code delivery, ownership, licensed third-party components and documentation are specified in the project agreement. We make those terms clear before work begins.
Is Xiaomei a released commercial project?
No. Xiaomei is presented as exploratory research and concept direction. It is intentionally distinguished from client delivery and completed engineering cases.
What happens when I submit the inquiry form?
The form opens a draft in your email app. Actual inbox delivery only becomes active after a verified production mail service is configured and tested.
Have a project, system or idea you'd like us to assess?
Start a project conversation ↗