Skip to content
LogiqDev

00The people who scope it, build it

Software, built by the
people who ship it.

Brief

Logiq Dev is a software studio in Dhaka, Bangladesh. We build MVPs, web platforms, and production systems — and an engineer, not a salesperson, replies to every brief within one working day.

Start

Start a projectOr judge us on the work first
Taking new projects
Local time
 
Next start
Next start date [Month YYYY]
Reply within
one working day
Timezone
GMT+6

Overlap hours

  • Central Europe (CET)13:00–19:00
  • UK (GMT)12:00–18:00
  • US Eastern (ET)08:00–12:00
  • Australia Eastern (AET)13:00–19:00
Founded
2019
Subcontracted
None
Based in
Dhaka
01Why Logiq

The advantages of staying small.

Every one of these is something a studio this size can promise credibly, and a two-hundred-person agency structurally cannot.

Senior people, doing the work

Everyone on the team is a senior engineer who does the building. There is no bench of juniors a salesperson hands your project to once the contract is signed.

Your code, your infrastructure

Every repository is yours from the first commit. Everything runs in your accounts and under your domains, not ours.

An engineer reads what you send

Briefs, questions, and weekly check-ins go to the person building your software — never a salesperson or an account manager relaying it.

Weekly demos, not status emails

You see progress on a working staging environment every week. What we built and what it cost stays visible the whole way through.

Selected work02

Products you can open and use.

Not screenshots of dashboards that never shipped. Each of these is live, and the client’s name is on it.

All work
03What we build

Four kinds of problems. One team for all of them.

Not a technology grid. Pick the shape closest to what you're trying to get built.

Building something that doesn't fit neatly into one of these? Tell us what you're building.

Who does the work04

These are the people who would write your code.

The whole team, not a shortlist — no mystery roster, and no handoff to strangers after the sales call. You get the people who do the work, which is the one advantage of a studio this size that actually matters.

See the whole studio

How this works

Step 01 / 0601Discover

01 / 06How this works

Discover

You send a brief — rough is fine. What you are building, roughly what you can spend, and when you need it. An engineer reads it and replies within one working day.

Step 02 / 0602Define

02 / 06How this works

Define

A call in your working hours, then a written scope with an estimate broken down by area. This part is billed, and credited back if you build with us. You own the document either way.

Step 03 / 0603Design

03 / 06How this works

Design

Before production code, we work out the product experience — the screens, the flows, and the states that are easy to skip until a real user hits them.

Step 04 / 0604Build

04 / 06How this works

Build

Your repository, your infrastructure, from the first commit. Small iterations, a working staging environment, and a demo every week. You always know what we did and what it cost.

Step 05 / 0605Launch

05 / 06How this works

Launch

We deploy it, watch how it behaves under real traffic, and fix what only shows up in production. Thirty days of fixes at no charge after handover.

Step 06 / 0606Grow

06 / 06How this works

Grow

A maintenance arrangement if you want one, and ongoing engineering when you need it. Most of our work now comes from clients we launched for years ago.

Start a project →

05How we work together

Three ways to start. One team behind all of them.

Pick the shape that matches what you already know about the project. The people and the way we work stay the same across all three.

Fixed-scope project

A defined build with a clear finish line.

Basis A fixed quote, held, after a scoping call

Monthly retainer

Ongoing work where scope moves week to week.

Basis A reserved block of capacity per month

Maintenance & support

Something we built, or something we've inherited and reviewed.

Basis [Flat monthly fee, quoted after a codebase review]

Not sure which one fits? Send the brief anyway — an engineer will tell you, and say so if it isn't for us.

06Straight answers

The things you are actually wondering.

How do I know the quality is real before I pay anything?

You don't have to take our word for it. Every project on our work page is a real product you can open and use, and we name the client. Ask us for a walkthrough of the code on any of them and we will do it on a call — not a prepared demo, the actual repository. If you want a smaller commitment first, take the paid discovery: a few hours of our time, a written scope you own, and no obligation to build with us.

You're a small team. What happens if one of you leaves?

It is a fair question and the honest answer is that we are small enough that losing someone matters. What we do about it: no project has a single owner, every repository is yours from the first commit, and everything runs in your accounts, not ours. If we disappeared tomorrow you would still have working software, your infrastructure, and a README that another team could pick up. We have been doing this since 2019 and the team page shows how long each person has been here.

Does the time difference mean I lose a day on every question?

No, because we do not work asynchronously by default. We are GMT+6, which gives us four hours of daily overlap with US Eastern and six with Central Europe, and we hold those hours for calls rather than for our own focus time. Anything you send outside them gets a reply within one working day. If your project needs more overlap than that, say so before we start and we will tell you honestly whether we can do it.

How much is a project going to cost me?

It depends on scope, not an hourly number times a guess, so the honest answer starts with a call. That first call is free. After it we turn your brief into a written scope with an estimate broken down by area, so you can see what each part costs and cut anything you do not need. The scoping work itself is billed and credited back if you build with us. You will have a real number before you commit to anything, not after.

What actually happens after I send a brief?

One of the engineers reads it — not a salesperson — and replies within one working day with either questions or a call invitation inside your working hours. On that call we tell you whether we think we are the right people, and we do say no. If it goes ahead, you get a written scope with an estimate broken down by area, so you can cut anything you do not need before committing.

00Start a project

Tell us what you're building.

Rough is fine. An engineer reads it — not a salesperson — and replies within one working day.

Start a projector hello@logiqdev.com
Reply time
one working day
Who reads it
An engineer
Sales calls
None