inbord for developers
An online space for your clients: scoping, access and delivery approval
With inbord, you open a space for each of your clients. Your client describes what they need, shares their credentials securely and approves each of your deliveries. They get in through a link, without creating an account.
Free, no credit card. Your client has no account to create.
Boreal Home
Shopify store + ERP connector · Go-live on November 12
Brief
The need in one sentence
Sync ERP stock levels with the store every 15 minutes.
Out of scope
The visual redesign and migrating old orders.
Files
Messages
The ERP API credentials are in the vault.
Perfect, batch 2 hits staging on Thursday.
30% deposit
Paid by card, held until approval
The usual problems
Scope creeps mid-project
New requests show up after the first deliveries, even though they weren't part of the original scope.
Credentials travel in plain text
API keys, hosting passwords and repository access are sent by email or chat, and trickle in one at a time.
QA is hard to follow
Bugs are reported by email, screenshot or word of mouth. Nobody knows what's fixed and what's actually a new request.
How it works with inbord
Your client gets a link. Everything else happens in their space.
- 1
Your client describes what they need
The need, the users, the tools to connect, and what's out of scope. Anything not listed is handled as an extra request.
- 2
Credentials in a vault
Hosting, repository, API keys, domain: your client stores their credentials encrypted, never in an email. A code for every view.
- 3
Your client approves each delivery
Each batch is uploaded as a deliverable, with its staging link or release notes. Your client approves, or asks for changes on that exact batch.
- 4
Feedback stays attached to each delivery
Feedback is attached to the delivery it's about, not scattered around. Once the last batch is approved, the project moves to “Delivered”, and the balance can follow by card.
The questions to ask in your brief
What a good brief should ask, for developers. With inbord, your client answers in their space, and you reuse the questionnaire on every project.
- What problem should the tool solve, and for whom?
- Which existing tools does it need to connect to (CRM, ERP, payments)?
- What's explicitly out of scope?
- Who holds access to the hosting, domain and code repository?
- Who tests and approves each delivery, and how quickly?
- Who handles maintenance after go-live?
Your questions
Is it safe to receive API keys through inbord?
That's what it's built for. Credentials go into an encrypted vault, and every view requires a code. A key sent by email stays readable in both inboxes.
Does inbord replace my ticketing tool?
No, and that's not the goal. Your Jira, Linear or GitHub stays the team's tool. inbord is what your client sees: the scope, their credentials, the deliveries to approve, without having to learn your tooling.
I work on retainer or monthly maintenance. Does it adapt?
Yes: a space can last. Your client finds every delivery and its history there, and you keep their credentials in the same place month after month.
