SORCERER
Get an estimate Estimate

Visual Effects

Transitions

Performance

Detecting performance...

Technology scenarios

These are situations a company might bring to us. They are hypothetical, and they are not case studies or claims about past work. Each one describes a bounded way we would approach the job. Duration and price are those of the related service; where that service has no published range, we quote after review.

Integration and data flow

You would like to connect your CRM to your manufacturing intake platform so new orders stop being re-keyed by hand.

We would write down the fields that move, the direction of the flow, and what happens when a record cannot be accepted. The engagement would deliver that connection and a handover, and it would leave warehouse, finance, and other systems unchanged. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include Salesforce, Microsoft Dynamics, REST, SQL Server, and .NET.

See this service Request an estimate

Your team keeps the operational record in spreadsheets, and you would like one shared database with a simple way to enter and look up the same facts.

We would name the workbooks that move, the columns that matter, and the checks that reject a bad row. You would receive the database, a small entry screen, and a note of what was imported, without a reporting suite. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include Microsoft Excel, SQL Server, PostgreSQL, and ASP.NET Core.

See this service Request an estimate

You would like paid orders from your online store to appear in your accounting system without a person exporting a file each morning.

We would agree which order events are in scope, how refunds are represented, and which cases a person still reviews. The result would be one connection and a short handover, not a replacement of either system. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include REST, Webhooks, SQL, and .NET.

See this service Request an estimate

Your staff sign in to two internal applications separately, and you would like one company login to cover both.

We would write down which application remains the source of accounts, which one trusts it, and which sign-in methods are out of scope. The engagement would finish with that connection and a note of how access is granted and removed. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include SAML, LDAP, Active Directory, and ASP.NET Core.

See this service Request an estimate

You would like a customer report in your support desk to open a tracked item in the tool your engineers already use.

We would name the fields that copy across, the statuses that stay independent, and the cases a person still handles. The work would be that one link and a handover, not a redesign of either queue. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include REST, Jira, and .NET.

See this service Request an estimate

AI and documents

Your team would like to ask questions of a bounded set of policy documents instead of searching a shared folder.

We would limit the assistant to the collection you provide, and we would say in writing what it must not answer from. You would receive the assistant and a handover that explains how the documents were loaded. The package and its published range are described under Private document assistant.

Typical technologies for this kind of work include PDF, PostgreSQL, Python, and .NET.

See this service Request an estimate

You would like a visitor to ask a question and receive an answer drawn only from pages already on your website.

We would name the pages that are in bounds, build that one assistant, and hand it over with a note of what it will and will not say. Other features of the site would stay as they are. The package and its published range are described under AI Enable my Site.

Typical technologies for this kind of work include HTML, JavaScript, ASP.NET Core, and Blazor.

See this service Request an estimate

Your team sorts incoming requests by hand, and you would like one step that suggests a category before a person confirms it.

We would pick a single workflow, define the categories, and leave the final decision with a person. The engagement would deliver that step and a handover, and it would not automate the rest of the process. The package and its published range are described under Add AI Capabilities to my Company.

Typical technologies for this kind of work include Python, .NET, and REST.

See this service Request an estimate

You would like staff to find a clause in a defined set of contracts without reading every file from the start.

We would bound the collection and describe what the assistant is allowed to quote from it. You would receive the assistant and the handover, with contracts outside that set left out of scope, and the assistant would not provide legal advice. The package and its published range are described under Private document assistant.

Typical technologies for this kind of work include PDF, Microsoft Word, PostgreSQL, and .NET.

See this service Request an estimate

You already ship a product, and you would like an assistant beside it that answers from your product documentation only.

We would agree the documentation set and the place the assistant appears, then build that feature and hand it over. The product itself would not be rewritten. The package and its published range are described under AI Enable my Site.

Typical technologies for this kind of work include REST, OpenAPI, JavaScript, and .NET.

See this service Request an estimate

Internal tools and automation

You would like estimators to enter a request once and produce a consistent packet for review, instead of copying between documents.

We would write the screens and the packet contents before any build, including what the tool will not calculate. You would receive the tool and a written list of what it does and does not do. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include Blazor, ASP.NET Core, SQL Server, and PDF.

See this service Request an estimate

Your stores count stock on paper, and you would like a small internal page where a count is entered and compared with the book quantity.

We would limit the tool to one count workflow and the exceptions it should flag. Purchasing, pricing, and the accounting close would stay outside the engagement. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include Blazor, ASP.NET Core, and PostgreSQL.

See this service Request an estimate

You would like a document to move through a short list of approvers, with a record of who accepted it and when.

We would name the steps, the roles, and the point at which the route stops. The tool would record those decisions and hand over with operating notes, and it would not replace your document store. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include ASP.NET Core, SQL Server, and SMTP.

See this service Request an estimate

Each week someone on your team pastes exports from three systems into one workbook, and you would like that workbook produced from the same files.

We would fix the three exports, the columns that are combined, and the checks that stop a bad file. The job would deliver that report and a note of the files it expects, not a live link to every source system. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include Microsoft Excel, .NET, and CSV.

See this service Request an estimate

Your coordinators book appointments from a shared inbox, and you would like one internal screen that shows openings and records the booking.

We would write down the hours, the resources, and the messages the tool sends. The tool would cover that desk only, and it would leave payroll and billing unchanged. The package and its published range are described under Custom internal tools.

Typical technologies for this kind of work include Blazor, ASP.NET Core, and SQL Server.

See this service Request an estimate

Modernization and migration

You have an internal site on an older ASP.NET stack, and you would like it to run on a current .NET release without changing what staff do in it.

We would list the pages that move, the pages that stay, and the behaviour that must match. You would receive the moved portion and a note of anything left on the old stack. Duration and price are set after review, as described under Move from one stack to another.

Typical technologies for this kind of work include ASP.NET, ASP.NET Core, C#, and SQL Server.

See this service Request an estimate

Your team still depends on a Windows desktop program, and you would like the same daily job available in a browser for remote staff.

We would name the screens that move in this engagement and the ones that remain on the desktop. You would receive those screens on the new stack and a note of what was left behind. Duration and price are set after review, as described under Move from one stack to another.

Typical technologies for this kind of work include Windows Forms, Blazor, ASP.NET Core, and SQL Server.

See this service Request an estimate

You rely on a Microsoft Access file as the system of record, and you would like the data and the daily tasks moved onto a server database with a small web front end.

We would begin with a short discovery review of the file, then inventory the tables and the tasks that are in scope. You would receive a quote for moving those parts, with anything left in the file listed as out of scope. Duration and price for the review are set after we see the system, as described under Old or unusual system.

Typical technologies for this kind of work include Microsoft Access, SQL Server, ASP.NET Core, and Entity Framework Core.

See this service Request an estimate

You would like one application that now runs on a machine in the office to run instead on a managed cloud service you can name.

We would write what moves, what stays on the office network, and how people will reach it afterwards. The engagement would cover that application and its handover, not every system around it. Duration and price are set after review, as described under Move from one stack to another.

Typical technologies for this kind of work include Windows Server, Amazon Web Services, Microsoft Azure, and Docker.

See this service Request an estimate

You still run a business process in a classic ASP page or an old Visual Basic program, and you would like a current application that performs the same process.

We would begin with a short discovery review of the program we can examine, then quote the move of the process you name. Features that nobody still uses would be written down as out of scope. Duration and price for the review are set after we see the system, as described under Old or unusual system.

Typical technologies for this kind of work include Visual Basic, Classic ASP, C#, ASP.NET Core, and SQL Server.

See this service Request an estimate

Reviews and rescue

You would like an independent reading of a codebase before a release, with the risks written in plain language and an ordered list of fixes.

We would review the architecture and the code you point us to, and we would deliver the written review only. Building the fixes would be a separate engagement. The package and its published range are described under Architecture or code review.

Typical technologies for this kind of work include C#, .NET, SQL, and Git.

See this service Request an estimate

You are considering a product or a codebase, and you would like a written view of how it is put together before you commit.

We would read what you are permitted to show us and write the risks and the questions that remain open. The review would not include a negotiation, a valuation, or a rewrite. The package and its published range are described under Architecture or code review.

Typical technologies for this kind of work include .NET, Java, SQL, and REST.

See this service Request an estimate

Your team started a rewrite that never reached its first release, and you would like that release finished.

We would assess where the work stopped and agree in writing on the release that is in scope. We would complete that piece and note what remains, and the engagement would not become open-ended staffing. Duration and price are set after review, as described under Rescue a stuck project.

Typical technologies for this kind of work include C#, TypeScript, SQL Server, and Git.

See this service Request an estimate

A vendor left an internal tool unfinished, and you would like it completed against a written list of what it must do.

We would separate what already works from what is missing, then write the finish line before any further build. You would receive that finished piece and a note of anything left outside the agreed finish line. Duration and price are set after review, as described under Rescue a stuck project.

Typical technologies for this kind of work include ASP.NET Core, Blazor, SQL, and Git.

See this service Request an estimate

Web and customer-facing

You would like customers to sign in and see the status of their own orders, with nothing more in the first release.

We would write the pages, the data they may show, and the accounts that are out of scope. You would receive that slice and a handover, not a full commerce site. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include ASP.NET Core, Blazor, SQL Server, HTML, and CSS.

See this service Request an estimate

You would like a form on your site that checks what visitors enter and sends complete requests to the people who act on them.

We would name the fields, the checks, and the destination. The work would stop at that form and its handover, and it would not include a marketing site around it. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include ASP.NET Core, HTML, JavaScript, and SMTP.

See this service Request an estimate

You would like a catalogue of products on the site you already have, with descriptions your staff can update.

We would bound the catalogue fields and the pages that show them, and leave the rest of the site unchanged. The engagement would end with the catalogue and notes for the person who edits it. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include ASP.NET Core, SQL Server, HTML, and CSS.

See this service Request an estimate

You would like visitors to request a time on your website, and you would like that request to land in the calendar your staff already use.

We would write down the fields the visitor sees, the calendar that receives the request, and the messages that are sent. Payment and any later reminders would be out of scope unless the written scope names them. Duration and price are set after review, as described under Something else.

Typical technologies for this kind of work include JavaScript, REST, ASP.NET Core, and Microsoft 365.

See this service Request an estimate

One step of your checkout fails in a known case, and you would like it fixed without rebuilding the storefront.

We would reproduce the case you describe, agree the behaviour that counts as finished, and hand over the change with a note of what was not redesigned. If the wider project has no finish line, it is not a fit for this service. Duration and price are set after review, as described under Rescue a stuck project.

Typical technologies for this kind of work include JavaScript, ASP.NET Core, REST, and SQL.

See this service Request an estimate

Hardware, devices and experiments

You would like one named measurement from a device you already own to appear on a screen your technicians use.

We would write the device, the measurement, the screen, and the conditions that count as finished. Cabling, certification, and any other measurement would be out of scope unless named. Duration and price are set after review, as described under Hardware, embedded, or a bounded experiment.

Typical technologies for this kind of work include C#, Serial communication, and TCP/IP.

See this service Request an estimate

You would like one change in device firmware, with a written test that says what passes and what fails.

We would name the device, the change, and the bench setup available for the work. The engagement would stop at that change and the notes that go with it, and it would not include a new board or a production line. Duration and price are set after review, as described under Hardware, embedded, or a bounded experiment.

Typical technologies for this kind of work include C, C++, and Embedded systems.

See this service Request an estimate

You would like a barcode scan at a workstation to look up an item and record that the step was completed.

We would specify the scanner, the lookup, and the record that is written. Inventory rules beyond that one step would stay out of scope. Duration and price are set after review, as described under Hardware, embedded, or a bounded experiment.

Typical technologies for this kind of work include .NET, SQL Server, and Barcode scanners.

See this service Request an estimate

You have a technical question that can be settled on a bench or in a short program, and you would like the question and the finish line written down before the work starts.

We would agree the question, the method, and the result that ends the engagement, including a negative result. You would receive the notes and the artifact named in the scope, and nothing open-ended beyond them. Duration and price are set after review, as described under Hardware, embedded, or a bounded experiment.

Typical technologies for this kind of work include Python, C#, and Serial communication.

See this service Request an estimate

Emerging technology, including quantum

You would like to know whether quantum computing can help with one optimization problem you can state precisely.

We would study that problem, build a bounded proof of concept with IBM Qiskit, and compare it with a strong classical approach on simulators and, where it makes sense, on IBM Quantum hardware. You would receive the proof of concept and a written assessment of whether a quantum approach is worth pursuing today. Duration and price are set after review, as described under Quantum computing exploration.

Typical technologies for this kind of work include IBM Qiskit and Python.

See this service Request an estimate

You would like a sampling or simulation question compared with a classical method, so you can decide whether a quantum approach is worth further work.

We would state the question in writing, build a bounded proof of concept with IBM Qiskit, and run the comparison on simulators and, where it makes sense, on IBM Quantum hardware. You would receive the proof of concept and a plain assessment, including the possibility that the classical method is the better choice today. Duration and price are set after review, as described under Quantum computing exploration.

Typical technologies for this kind of work include IBM Qiskit and Python.

See this service Request an estimate

You would like to know whether a small language model running under your own control can perform one named task on a sample of your documents, before any larger build.

We would define the task, the sample, and the comparison that ends the work. You would receive the prototype and a written note of what it did and did not do on that sample. A production assistant, if you want one later, is a separate package, and duration and price for this prototype are set after review under Something else.

Typical technologies for this kind of work include Python, PyTorch, and .NET.

See this service Request an estimate

Something went wrong. Reload this page and try again. Reload 🗙