Make room for choice
Homes and businesses choose the help they need. Independent professionals choose their availability, coverage and the requests that suit their business.
INSIDE KNOQ · OUR PRODUCT RECORD
Product principles
and development history.
The idea we are building, the choices behind it, and the milestones we can substantiate.
KNOQ is being built to connect households and businesses that need local help with independent trades and service professionals who have the skills and time to offer it.
Both sides have a choice. A useful connection needs agreement.
THE PRINCIPLES
Useful for both sides.
Respect the commitment
Availability starts the conversation. In the planned initial trial, the professional proposes scope, price and timing; the customer explicitly accepts to confirm the booking. An assessment does not authorise repairs.
Keep privacy in the journey
The planned experience limits when precise location is shared. Live travel progress stops at arrival, before completion or review.
Start local and learn
Interest across Perth’s northern suburbs helps shape the local trial. Evidence from households, businesses and independent professionals should guide what comes next.
Independent professionals set their own prices and remain responsible for their credentials, insurance and work. Optional memberships do not buy priority or guarantee work.
THE CONNECTED JOURNEY · PLANNED EXPERIENCE
From a need to an agreed next step.
This account draws together the journey already described on KNOQ’s website. Request choices are alternatives; the numbered stages show how a job is intended to progress.
A home or business describes the need
Choose the service and ask for help soon, arrange a time, or request a quote first. Those are three ways to begin, not three steps every request must take.
A professional considers the fit
The professional chooses their available time and service area, reviews the request and decides whether the work fits. They can propose scope, price and timing, suggest another time or pass.
Both sides agree what happens next
For the planned initial trial, the customer explicitly accepts the professional’s scope, price and timing to confirm the booking, subject to eligibility and availability. An assessment has its own agreed scope, timing and any fee; repairs need a separate proposal and agreement. If nobody suitable is available, another time can be explored.
Location follows the commitment
Before the customer accepts the proposal, the job location is approximate. Booking confirmation releases the exact address to the booked professional. During the planned initial trial, KNOQ fees are waived and customers pay professionals directly for agreed work.
See the current trial and pricing explanation for the applicable stage and conditions.
Travel progress ends at arrival
In the planned journey, the customer can follow the agreed job’s travelling status until arrival. Provider-backed road routes, traffic-aware arrival estimates and turn-by-turn navigation are not active. Live-trip sharing stops when the professional arrives.
The work is checked, then reviewed
The planned journey continues through checking the work, confirming completion and leaving feedback tied to that KNOQ job. Completion and review do not extend live-trip sharing.
Availability and timing depend on suitable local supply and professional confirmation. For a question, correction or help with your expression of interest, contact KNOQ Support.
Watch or read the existing explanation
The 90-second film and transcript and four concept films with captions and transcripts explain the proposed experience. Their illustrations do not demonstrate a live marketplace.
CLEAR STATUS
What the demonstrations mean.
- Public today
- The website, professional and community expressions of interest, and enquiry routes. These are separate from booking services.
- Planned and illustrated
- The full request-to-review journey above. Concept films and phone-shaped illustrations explain the intended experience.
- Development demonstrations
- The website labels its Android completion and review screens as development screens, not live job information. They do not establish that the full journey is operational.
- Private app preview
- The current app privacy notice describes invited preview access to sign-in, account/profile synchronisation and catalogue browsing. New jobs, professional availability, payments and notification registration remain closed. Account deletion is not operational yet.
RECORDED MILESTONES
A dated account, with clear limits.
In 23 days, KNOQ moved from a marketplace idea, its first domain and a simple coming-soon site to a public website inviting people into what comes next. The dates below show that momentum — and the limits of what each milestone proves.
An idea found its name and a home
The marketplace concept was taking shape in a ChatGPT conversation titled Assist app concept. Early working names included Assist and Ping. By late afternoon, a KNOQ business-name application had been submitted and knoq.au had been successfully registered.
That same day, the first KNOQ website — a simple coming-soon page for private sharing — reached its first Netlify production deploy at approximately 4:58 pm AWST. Its browser title was KNOQ — Coming soon, and it opened with the line Help nearby. Right when it matters.
The site was configured for knoq.au, but DNS and TLS were still propagating. The time above is therefore the first hosting-deployment time, not proof of the exact instant knoq.au became publicly reachable.
That makes 16 August the first substantiated KNOQ day in this record: an idea becoming something named, visible and ready to build. It is not a claim about the exact moment the name was coined.
KNOQ became a registered business name
By 18 August, KNOQ’s registered business-name status had been published on the website. KNOQ is a registered business name operated by Steve Harley under his ABN; it is not a separate company.
The first product foundations
Repository history records the first KNOQ Android and API foundation on 21 August, followed by the native iOS foundation on 22 August.
These were development foundations, not evidence that a public marketplace was operating.
Three Australian domains secured
knoq.com.au and knoq.net.au were both successfully registered. Together with knoq.au, this created KNOQ’s three-domain Australian home.
Domain registration secures web addresses. It does not establish trade mark rights or exclusive rights to a business concept.
Official public website and expressions-of-interest launch
Password protection was removed from the public website pages. KNOQ’s preserved release-check records show successful anonymous access checks at approximately 5:06 pm AWST (UTC+8).
This milestone concerns the website and expressions of interest. Household bookings were still coming soon.
The check time is not the exact instant the password was removed.
Trade mark application lodged and this record expanded
KNOQ lodged Australian trade mark application 2695639 for the plain word mark KNOQ in Classes 9 and 35. The application is pending examination by IP Australia. Lodged does not mean registered.
The first edition of this product record was prepared and published on 10 September. Edition 2 expanded the dated account with the substantiated origin, domain, first-hosting and product-foundation milestones above.
Safer foundations, tested across both apps
KNOQ strengthened the private-preview foundations across Android, iOS and the connected service. Testing covered clearer quote and cancellation recovery, protected address selection, travelling-status safeguards and matching behaviour across both native apps.
The routing work remains deliberately dormant. Address selection uses an opaque, short-lived receipt, and any future route result is designed to be encrypted and expire. Provider-backed road routing, traffic-aware arrival estimates and turn-by-turn navigation are not active.
Android Build 163 was signed locally but not uploaded. iOS Build 163 was source-frozen but not archived. Payments, operational account deletion, public marketplace access and guaranteed professional availability remain closed. This records verified development progress, not a public product launch.
NATIVE APP DEVELOPMENT · FOUNDATION SPRINTThe apps take shape.21 August–10 September 2026 · 10 milestones across Android and iOS
In nineteen days, two native applications moved from foundations to privately tested release candidates. The record below celebrates that pace without calling a development build a public launch.
iOSAndroid™KNOQ-designed markers · no Apple or Google endorsement implied
Android development begins
KNOQ’s first native Android foundation was committed in Kotlin and Jetpack Compose. Separate development and staging environments followed immediately.
iOS joins the build
The native Swift and SwiftUI foundation arrived the following morning. Authentication, customer and professional journeys, notifications and travelling-location behaviour began converging around a shared API contract. A platform-parity release gate was established the same day.
The first shareable app
An early Android staging build—KNOQ Version 9—was distributed privately through Firebase App Distribution. Request creation and authoritative live-trip mapping then became working parts of the Android development journey.
From prototypes to controlled releases
iOS reached scenario parity, an isolated Google Play internal build was prepared, and both applications gained stronger arrival-assurance, verification and fraud-control foundations.
Norb is born
Norb was introduced across the native applications as KNOQ’s service guide. Ask Norb entered staging, followed by the approved V8 character and waiting-animation package. This is the strongest evidence-backed date for Norb’s introduction.
Real devices, matched experiences
The Mac Mini became KNOQ’s authoritative iOS build host. Scheduling, cancellation, visual parity and the live-trip privacy lifecycle were exercised across physical Android and Apple devices—including ending precise location sharing on arrival.
Messaging, notifications and navigation
Protected messaging, iOS push notifications and appointment recovery matured across both platforms. The iOS journey gained native Apple Maps handoff while continuing to protect the active travel-location session.
The complete service journey takes shape
Testing expanded across phones and tablets. Quote review, competing acceptances, work agreements, invoices, visit timing and encrypted visit details were added. A Stripe sandbox foundation was created but remained deliberately dormant—not a live payment service.
Private production preview
Recovery and support controls were strengthened, a private Google Play testing link was issued, and signed iOS production candidates were archived. iPad support, Apple privacy declarations and later Android candidates followed. These were private testing and store-readiness milestones—not public store launches.
The Mapbox foundation is laid
KNOQ’s Mapbox account was secured, a Signal Noir map style was published, restricted development credentials were prepared and an address-integration package was completed. Native integration and device verification were still pending, so this records the Mapbox foundation—not completed app integration.
Apple, App Store and iOS are trade marks of Apple Inc. Android and Google Play are trade marks of Google LLC. Platform names are used only to identify KNOQ’s development work. The device markers are KNOQ artwork, not platform logos or store badges.
Evidence for the added milestones comes from dated source-thread, repository, hosting and account correspondence. Private receipts, reference numbers, addresses, tester identities, credentials and billing details are not published. Development and earlier sharing preceded the official launch. This record does not establish the earliest date on which any KNOQ idea or feature became public. Historical dates above refer to the events described, not the publication date of this page.
EDITIONS AND CORRECTIONS
A record that can be followed.
Update prepared 16 September 2026. Clarifies the planned initial-trial agreement, assessment, address-release and direct-payment sequence. These are approved design requirements, not a claim that the marketplace is open. The recorded milestones and earlier editions below are unchanged. Read the short trial guide.
Edition 4 · first published (AWST). Added the verified Build 163 development milestone, including protected address and travelling-progress foundations, cross-platform qualification and the capabilities that remain inactive. Read the retained fourth edition.
Edition 3 · first published (AWST). Added the expandable native-app foundation sprint, ten evidence-backed Android and iOS milestones, KNOQ-owned platform markers and clear trade-mark and capability limits. Read the retained third edition.
Edition 2 · first published (AWST). Expanded the dated account with KNOQ’s first substantiated day, registered business-name status, domain portfolio, first website deploy, product foundations and pending trade-mark application. Read the retained second edition.
Edition 1 · first published (AWST). Prepared on 10 September 2026. Read the retained first edition.
Later material changes will identify what changed and retain earlier public editions where privacy and rights permit. A correction will distinguish a corrected historical fact from a new product development.
This page records KNOQ’s product approach and history. It makes no claim of exclusive rights over the marketplace concept. To suggest a correction, contact KNOQ Support and identify the passage and supporting information.
Founded and owner-operated by Steve Harley.
Steve is KNOQ’s Founder & Venture Architect and remains accountable for its direction. KNOQ is a registered business name operated by Steve Harley, ABN 40 673 535 778.
Read about Steve and the purpose behind KNOQ