Sophura is David Kumi — one engineer who fixes dated regulatory obligations in other people's products for a fixed fee and documents the fix. I work on GMT+0 from Accra — the same clock as London, an hour behind Berlin. Your working day is my working day. No team page and no testimonials: what the desk has instead is a sourced ledger, published prices, and evidence packs you can inspect.
Why a “deadline desk”?
Because that is the actual shape of the problem. Compliance advice is plentiful; what businesses facing a dated obligation struggle to buy is the implementation — someone who will make the change in the product, verify it, and hand over a dated record. Consultancies recommend and law firms opine; this desk edits the code and writes down what was done. The ledger is the operating system: each obligation, its date, who it binds, what it requires, and a source you can open.
Where is the desk, and how do the hours work?
I work the European business day on GMT+0 — your working day is my working day, which is why this desk covers European obligations. Working day 09:00–17:00 UTC (GMT+0) — the European business day. Email answered within one business day. Engagements are billed and contracted through Sophura LLC, a Wyoming (US) company; work happens in your systems, under your access controls, in your timezone's working day.
Why should you believe a desk with no case studies?
The fair question, answered without a logo wall.
You shouldn't take it on faith — that is the point of how this site is built. There are no invented clients and no testimonials here, because the obligations this desk serves are new enough that nobody has a long track record on them, whatever their pricing implies. What you can verify before paying anything: every statistic on this site links to a named source with a retrieval date; every price and duration is published; a sample evidence pack is available on request; and this site itself passes the accessibility and security standards it sells — check the accessibility statement, the security.txt and the response headers.
How is client access protected?
The question every client should ask a one-person supplier, answered in one paragraph: work happens on a full-disk-encrypted machine; credentials live in a password manager behind hardware-key authentication, never in plaintext or chat logs; each client gets a separate browser profile; access is requested at the minimum scope that does the job and returned when the job ends; and a written first-hour incident procedure exists — if something ever goes wrong on my side, you hear it from me first, in writing.
What does the desk deliberately not do?
- No legal advice. I find the specific obligation you are breaching, fix it for a fixed fee, and hand you the evidence. I don’t give legal advice. That line is on every page because it is the operating boundary, not a disclaimer.
- No conformity attestations. I implement and document; I do not sign declarations of conformity.
- No retainers, no hourly billing. Fixed fee, fixed duration, stated exclusions — the whole ladder is public.
- No AI chatbot on this site. A compliance question deserves a considered written answer, not a widget's guess — and a desk that sells Article 50 work is not going to model casualness about AI interfaces on its own site.
Last reviewed· Every dated claim on this page links to its source.