Loading
Software engineering
A Bangladesh-based engineering team building web, mobile and platform software for businesses across Europe and beyond. You file a brief, we come back with a scope and a number.
Specific commitments, each backed by something already built.
Legal
We sign before you describe the problem, not after you have already described it.
Data
Export or erase your data from your dashboard. Invoices are retained only as long as tax law requires. One month to respond, in writing.
Access
Two-factor on every account. Revoke a device and it is out on its next request, not at the end of a token's life.
Record
Every consequential action is logged against the person who took it, and you can see your own.
Five steps, no surprises in the middle.
01
An account on your own dashboard, not an email thread.
02
Two-factor from the first sign-in. Recovery codes, no SMS.
03
Describe the problem. Pick a service or write your own.
04
Written, itemised, and agreed before anyone writes code.
05
Work lands in pieces you can see. You are invoiced against what has already been delivered.
Changes to scope are re-quoted rather than absorbed — which is slower when requirements move a lot.
Needs someone on your side available to make decisions.
Not a route to new features — those get scoped separately.
Everything about your project lives in one account you control, and stays there after the work is delivered.
Your dashboard
Milestones, invoices and activity in one place, from the day the project starts.
If yours is not here, ask it — we will add it.
You create an account and file a brief describing the problem. We come back with a written scope, a number and a rough timeline before any work begins. If it looks right, we turn the brief into a project with milestones you can track from your dashboard.
Yes, and before the scoping call rather than after it. Send yours or ask for ours.
We are in Bangladesh, UTC+6. That gives a working overlap with most of Europe every afternoon our time. Everything consequential is written down in the project rather than said on a call, so a missed hour does not cost a day.
Writing
Either fixed scope, agreed and itemised before work starts, or per milestone on an ongoing engagement. Both are quoted in writing. We do not quote a price against an undefined scope, because that price is always wrong for one of us.
Against completed milestones. Each milestone is visible in your dashboard before it is invoiced, so you are paying for something you have already seen. Invoices are settled off-platform — bank transfer, Payoneer or PayPal.
You are told before the due date, not after it, with what changed and what it means for the ones after. A milestone that has not been delivered is not invoiced.