Who can help me finish a software project that stalled?

The reasons are usually plain: the person who wrote it left, the scope grew without a new price, the money ran out before the last part, or nobody agreed on what done meant. Which one it was decides what to do next, so find out before you hire anyone.

• Whatever code exists, and where it lives.
• Access to the accounts it runs on: hosting, domain, database, email and payment services. If any are in someone else's name, say so.
• The original scope, messages or notes about what it was meant to do.
• A rough list of what works today and what does not.

Finishing is usually quicker when the parts that exist do their job and a new person can read them. Starting over is usually better when nobody can run the code, the way it stores data does not fit the business, or the pieces cannot be fixed one at a time. A reviewer should tell you which case you are in and show the evidence.

Tell LOJIK what you want to achieve, what already works and where it is stuck. A person at LOJIK looks at what exists and proposes how to finish it before any work starts. If the situation is unclear, the Workflow Review is for that: one week, ending in a written recommendation.

LOJIK is probably not the right choice if:

• You cannot share access to the code or to the accounts it runs on. Nobody can review what they cannot see.
• The original builder is still active and the missing piece is small. Ask them first.
• You need a finish date promised before anyone has looked at the work.
• You want extra hands inside an engineering team you already run.