makeenology.orgboot_sequence.sh

$ open makeenology.workspace

[01] prepare workspace...
[02] load project index...
[03] mount interface...
[04] ready for input...
system_load000%

process: loading

inspect services/

Your next website.
Your next system.

From custom websites and e-commerce to AI search and production software. I connect the experience people see with the engineering that makes it work.

~/services/websites01.service

What I build

Websites & e-commerce

Distinctive, fast websites that make a business easier to understand, browse, and contact.

From a lodge's accommodation and enquiry flow to a searchable publishing archive: I handle design, development, content structure, and the tools needed to run the site.

Useful outcomes

  • Custom business, institutional, publishing, and hospitality websites
  • Storefronts with clear product browsing and WooCommerce integration
  • Legacy migrations that preserve content, media, and important URLs
  • Editable content, responsive layouts, accessibility, and search foundations

Typical system components

Next.jsWordPressWooCommercePHPTypeScripttechnical SEO
~/services/knowledge-systems02.service

What I build

AI knowledge systems

Private, source-grounded assistants and research tools built around your documents, data, and workflows.

For organizations with valuable internal knowledge that generic AI tools cannot represent safely or precisely.

Useful outcomes

  • Make internal knowledge searchable and usable
  • Return answers with inspectable source context
  • Give teams one reliable interface for fragmented information

Typical system components

RAGcitationsrerankingevaluationstructured output
~/services/search-retrieval03.service

What I build

Search and retrieval infrastructure

Semantic, full-text, and hybrid search systems for large or multilingual collections.

For products whose users need to find the right passage, record, answer, or document—not merely a plausible result.

Useful outcomes

  • Improve relevance across difficult document sets
  • Support natural-language and exact-term discovery
  • Build retrieval foundations that can grow with the corpus

Typical system components

PostgreSQLpgvectorHNSWRRFhybrid search
~/services/document-intelligence04.service

What I build

Document intelligence

Ingestion systems that turn PDFs, scans, audio, and inconsistent source files into structured, searchable data.

For teams with a large archive or recurring document workflow that cannot be solved by manual processing.

Useful outcomes

  • Convert archives into a usable digital corpus
  • Automate repetitive extraction and processing work
  • Preserve provenance from source file to indexed passage

Typical system components

OCRtranscriptionparsingchunkingmetadata pipelines
~/services/custom-products05.service

What I build

Custom AI software

Purpose-built SaaS products, internal tools, and workflow automation around a specific operational problem.

For founders and teams who know the workflow they need to improve and want an engineer who can own the system end to end.

Useful outcomes

  • Replace fragile manual processes with dependable software
  • Connect AI capability to an actual user workflow
  • Ship a maintainable product instead of a disconnected prototype

Typical system components

Next.jsAPIsautomationauthenticationsubscriptions
~/services/backend-cloud06.service

What I build

Backend and cloud systems

The databases, APIs, security controls, deployment, and operational foundations behind production software.

For teams that need the surrounding system—not only the model call—to be secure, observable, and maintainable.

Useful outcomes

  • Move a prototype toward production reliability
  • Design data and API boundaries for future growth
  • Reduce infrastructure fragility and deployment friction

Typical system components

PostgreSQLDockerLinuxCloudflaresecurity

cat delivery.process

A practical path from uncertainty to production.

The shape changes by engagement, but the work stays anchored to the problem, the source data, and a verifiable definition of useful.

  1. 01

    Understand the brief

    Talk through the audience, existing content or data, and what a useful outcome looks like.

  2. 02

    Design the experience

    Work out the structure, interface, and technical approach before adding complexity.

  3. 03

    Build and verify

    Implement the product in testable increments, evaluate quality, and keep source behavior inspectable.

  4. 04

    Deploy and improve

    Ship the system, monitor the workflow, and refine it against real use rather than demo assumptions.

./scope_project.sh

Let's work out what you need.

Tell me about your business, your website, or the workflow you want to improve. We can take it from there.

Discuss a project