Work | 3Knots Digital

01 AI · Property

Automated object detection for property workflows.

A United States property ops team needed objects on appraisal photos named in the workflow — roof, HVAC, garage — so a reviewer could finish the pass without a second tool. We wired the model to the media they already collect and left a named owner on the release.

Field photos, a review queue, and a clock. If the model cannot sit inside the listing or appraisal screen they already open on Monday, it is not a product.

Artificial Intelligence Web development Brand & Creative

Market: US property ops
Stack: Vision · Python
Outcome: Review in the workflow

01 Vision in the workflow Objects named on the photo set the desk already collects — scored, not staged.
02 A review screen they know The queue, the comps, and the publish path stay in one product.
03 A named owner Evals, prompts, and the repo transfer. We do not hold the model hostage.

Faster review Manual passes drop when detection lives on the desk, not in a slide.
Owned product Source, prompts, and evals transfer with the delivery.
US-hour coverage A desk that can run the product when stakeholders are awake.

02 Web · SaaS

Web application and admin as one system.

A SaaS team hired us when the marketing site, the product, and the admin no longer looked like one company. We designed and engineered them in the same loop — tokens in the repo, weekly demos, then a live URL.

A founder or product lead with a date, a stack, and a stakeholder who will ask for the live URL. Not a brand deck and an offshore build that never meet.

Web development Brand & Creative Artificial Intelligence

Market: US SaaS
Stack: React · Laravel
Outcome: One system

01 Product website Positioning, IA, and a front-end that holds under campaign traffic.
02 Authenticated tools The desk that publishes, bills, and reviews — one system with the site.
03 CI and a date Automated checks, a human pass, then a named owner on the URL.

One system Brand site and product tools share type, color, and components.
You own the repo Source and the production environment transfer with delivery.
A date on the wall Weekly demos. No vendor maze between design and engineering.

03 Apps · Retail

iOS and Android as one product, not a wrapper.

A retail team needed the app to look like the site and the bag. We shipped native-quality flows with a shared system — QA on the glass people actually hold, then a named owner on the listing.

A launch date, a catalog, and a brand that already exists in the room. The app cannot invent a second company.

Mobile apps Brand & Creative Web development

Market: US retail
Stack: Swift · Flutter
Outcome: Store-ready

01 Jobs first The paths a buyer finishes on day one — not a screen dump.
02 Shared tokens The same type and color as the site, on iOS and Android.
03 A listing that ships Device matrix, regression, and a human pass before review.

One house Site, app, and pack share the same system.
Held on real glass QA on the devices your users actually hold.
A named lead One owner from brief to the listing.

04 Logos · Firms

Marks that hold from 24px to a campaign wall.

A professional firm needed the letterhead, the site, and the client portal to look like one practice. We locked the mark, built the kit, and left files they can reprint.

A name that already has weight. The identity has to hold in a boardroom — not a template with a stock serif.

Brand & Creative Web development

Market: Professional firms
Stack: Identity · Print
Outcome: Files you reprint

01 A mark that holds Drawn to survive 24px, an app icon, and a campaign lockup.
02 Stationery and icons The files a firm reprints without opening a ticket.
03 Rules on paper Clear space, color, and type — written so the site can follow.

Firm mark

One practice look Mark, site, and portal share the same system.
Files you can reprint Identity transfers. The firm owns the work.
Holds at 24px The mark still reads as a favicon.

05 Design · Product

Product UI that matches the brand on the wall.

A product team asked for a redesign that would survive engineering. We mapped the flows, locked the system, and sat in the same review as the build — so the UI did not die in a hand-off folder.

A stakeholder who will click the live product, not a Figma prototype that never ships. Design has to sit with engineering.

Brand & Creative Web development Mobile apps

Market: US product teams
Stack: UI · Design system
Outcome: One conversation

01 The jobs first The paths a user finishes — then the components.
02 Tokens in the repo Type, color, and components that engineering can actually use.
03 One review Design and build stay in the same conversation to launch.

One system Campaign and product share the same tokens.
Ships with the build No hand-off folder between design and engineering.
A named lead One owner from the first flow to the live URL.

06 eBook · Desks

Covers, interiors, and the desk that ships them.

A United States publishing desk needed titles finished on every glass without three vendors arguing over the same mark. We took cover, interior, catalog, and the author platform as one brief.

A pub date, a title list, and a desk that cannot wait on a brand agency to discover what an eBook file is.

eBook publishing Brand & Creative Web development

Market: US publishing
Stack: Covers · Interiors
Outcome: Catalog-ready

01 Cover to interior Market-ready files a store will accept — not a PDF that dies in conversion.
02 Author platform The site the imprint actually publishes from, wired to the book.
03 A date that holds Weekly proofs and US-hour coverage so the catalog does not wait.

One title system Cover, interior, and listing share a file path.
A date that holds Weekly proofs. The pub date is a constraint.
You own the files InDesign, print, and the store package transfer.

Selected work.