[07]FAQ
The awkward questions,
answered in writing
Everything here also appears contextually inside service pages — this is the printable version. If your question resists a short answer, it probably deserves an email.
Before you ask
How do you work with international clients?
- Remote-first: two fixed daily overlap windows with your region, one shared milestone board, and a written weekly note — shipped, blocked, next. Decisions live in documents, so nothing waits on a meeting.
I see Firebase mentioned — is the backend already built?
- This site launched frontend-first: content runs through a typed, adapter-based layer with a local source. The Firebase integration (Firestore content, Auth-based admin, Storage media) is the planned next phase; nothing in the UI will need rewriting for it.
How do we start?
- Send the rough version — a paragraph, a spreadsheet, a napkin photo. Within one working day you get either a discovery proposal or a straight 'we're not the right fit, try this' — both are useful answers.
Services & teams
Who owns the code, accounts and store listings?
- You do, from day one. Repositories, cloud projects and store accounts are created under your organisation; we collaborate inside them. That includes design files, documentation and any admin tooling we build for you.
Which mobile stack will my app use?
- Our default is React Native or Flutter for product coverage at realistic budgets; native Kotlin when performance or deep OS integration justifies it. We maintain production apps in this family ourselves, so recommendations come with maintenance numbers, not vendor slides.
How do you work with international clients?
- Remote-first: two fixed daily overlap windows with your region, one shared milestone board, and a written weekly note — shipped, blocked, next. Decisions live in documents, so nothing waits on a meeting.
I see Firebase mentioned — is the backend already built?
- This site launched frontend-first: content runs through a typed, adapter-based layer with a local source. The Firebase integration (Firestore content, Auth-based admin, Storage media) is the planned next phase; nothing in the UI will need rewriting for it.
How do we start?
- Send the rough version — a paragraph, a spreadsheet, a napkin photo. Within one working day you get either a discovery proposal or a straight 'we're not the right fit, try this' — both are useful answers.
Do we actually need AI features in our product?
- Sometimes — and we audit before you buy. The test is a workflow where text, documents or judgement are the bottleneck: support deflection, drafting, classification, search over your own corpus. If the win is a slide rather than a saved hour, we write it into the skip-list and ship deterministic code instead. The audit is billable, short, and honest by design.
Money & process
How do you price projects?
- Fixed scope against a signed brief, split into milestone payments. After discovery you get a number, not a range. If scope changes later, it is priced in writing before work starts — the change rate is agreed in the same document so nobody negotiates under deadline.
How do you work with international clients?
- Remote-first: two fixed daily overlap windows with your region, one shared milestone board, and a written weekly note — shipped, blocked, next. Decisions live in documents, so nothing waits on a meeting.
I see Firebase mentioned — is the backend already built?
- This site launched frontend-first: content runs through a typed, adapter-based layer with a local source. The Firebase integration (Firestore content, Auth-based admin, Storage media) is the planned next phase; nothing in the UI will need rewriting for it.
How do we start?
- Send the rough version — a paragraph, a spreadsheet, a napkin photo. Within one working day you get either a discovery proposal or a straight 'we're not the right fit, try this' — both are useful answers.
Security & data
How do you work with international clients?
- Remote-first: two fixed daily overlap windows with your region, one shared milestone board, and a written weekly note — shipped, blocked, next. Decisions live in documents, so nothing waits on a meeting.
How is my app or admin secured?
- Authentication with role-based access (custom claims), database security rules maintained as code and tested in CI, server-side validation on every input, and a documented backup/restore drill before handover. We provide the rule files and the drill notes — you can audit them any time.
I see Firebase mentioned — is the backend already built?
- This site launched frontend-first: content runs through a typed, adapter-based layer with a local source. The Firebase integration (Firestore content, Auth-based admin, Storage media) is the planned next phase; nothing in the UI will need rewriting for it.
How do we start?
- Send the rough version — a paragraph, a spreadsheet, a napkin photo. Within one working day you get either a discovery proposal or a straight 'we're not the right fit, try this' — both are useful answers.
Where does our data go when AI features are used?
- Only where the contract says it goes. Default posture: provider APIs with no-training settings, keys and retention configured per agreement, PII minimised or redacted in the pipeline, and a written data-flow note in the repo. If a use case needs zero-egress, we price on-device or self-hosted options instead of pretending the cloud is free.
Still open-ended? That's the point of discovery — bring the ambiguity, we'll price the clarity.
Ask us directly →