TERAJUWORKS is a founder-built construction technology platform for homeowners and contractors. It connects structured project input, cost estimation, confirmed project value, contract, execution, progress and construction intelligence in one ecosystem.
RM1M is an indicative 12-month investment case. Final valuation, instrument, ownership, IP structure and terms remain subject to due diligence and investor discussion.
A shared project-planning and costing foundation with different permissions and workflows for homeowners and contractors.
TERAJUWORKS is currently operated under TERAJU CIPTABINA RESOURCES during its founder-controlled, bootstrapped stage. The construction company is the early operating environment and a potential customer/contractor; it is not the technology investment target.
Software, technology product, ecosystem, technology team, commercialisation, IP and scalable growth.
Design & Build / construction operations that may use TERAJUWORKS and provide real-world validation.
Capital-efficient product development and live construction-domain validation.
12-month case to formalise, commercialise and scale.
Appropriate corporate, IP, governance, financial, product and commercial structure.
Common founder ownership and related-party relationships are disclosed. Future IP assignment/licensing, transactions and entity restructuring should be documented through appropriate professional and legal processes.
The key transition is from founder-led product construction to measurable adoption, monetisation, repeat usage, independent contractor participation and scalable execution.
Core product, planners, costing and project-control architecture exist.
Project information is increasingly linked from estimate to contract, work and progress.
Early registrations and product usage provide an initial market signal; paying adoption remains unproven.
Investment is intended to reduce founder dependency and build repeatable growth.
The platform is structured around a continuous project reference rather than isolated calculators.
The current product connects manual project input with AI-assisted floor-plan extraction, local-first IFC room/area import, canonical calculation rules, costing, contract control and project intelligence.
Users can define rooms/areas directly and generate construction or renovation budgets from calculation rules.
The floor-plan workflow can extract room names, areas, dimensions and confidence for review before planner import.
IFC Room / Space data can be extracted, reviewed, edited and handed to BuildPlanner or RenovationPlanner.
The current IFC bridge stores the source file locally in browser IndexedDB and does not send the BIM source through the server/database import path.
Admin-managed calculation rules and rate sets are intended to remain the source for budget and Cost Estimate calculations rather than duplicating business logic across screens.
BuildPlanner: Built-up Area + one new-construction RM/sqft context. RenovationPlanner: Existing Area + Existing RM/sqft and New Area + New RM/sqft remain separated.
TERAJUWORKS is being designed so the same structured project reference can move from measurement and costing into contract, execution and insight. Over time, project activity and approved rate observations can create a stronger intelligence layer — subject to data quality, permissions and commercial validation.
Rooms, areas, quantities, rates, items and confirmed values are structured instead of remaining only in documents or spreadsheets.
The product is designed to carry the same project baseline into contract, programme, progress and insight.
State-based rates, contractor observations and project records can progressively strengthen decision support as the network grows.
This is a product thesis and future value proposition, not a claim that a mature data network or network effect has already been achieved.
The repository shows a progressively connected contractor control architecture rather than isolated schedule pages.
Cost Estimate is converted into a confirmed contract baseline, with versioned amendment history.
Work Program is validated against the confirmed contract and Progress uses server-persisted project-control records.
Planned and actual progress are reconciled into S-Curve and Project Insight views.
Payment administration is a product direction, not a claim that TERAJUWORKS currently operates regulated escrow or fund-holding services. Any payment-processing or disbursement model requires appropriate legal and regulatory structuring.
Registered accounts, planner records and profile information are managed through the Admin environment.
Admin controls the calculation-rule source used by the costing layer, with separate renovation rule handling.
Default and state/Wilayah rate sets, comparison and contractor market-related controls are part of the platform architecture.
Development milestones and source changes are recorded in the repository data layer for traceability.
GitHub main is used as the source/data foundation, GitHub Pages serves the frontend, and Vercel API functions provide controlled server operations. Project Control records are persisted server-side rather than relying only on browser localStorage.
These are commercial pathways being developed and validated; they are not presented as proven recurring revenue today.
Potential paid estimate, planning and project-preparation services.
Potential recurring software plans for contractors and project teams.
Potential platform, project-management or transaction charges where projects are facilitated.
Structured contractor rate observations can strengthen state-based estimation intelligence over time.
A homeowner can begin with costing and planning, then potentially proceed to a construction provider. If the provider is TERAJU CIPTABINA RESOURCES, that construction revenue belongs to the separate construction business and should not be presented as TERAJUWORKS software revenue.
The platform can potentially connect homeowner demand with independent contractors. TERAJU CIPTABINA RESOURCES may participate as one contractor subject to the same applicable platform rules and related-party arrangements.
Registered-account KPIs below are linked to the Admin Database rather than manually hard-coded.
Account counts are live database indicators. Social metrics are point-in-time marketing observations and are not equivalent to active users, retention, revenue or conversion.
The roadmap prioritises the workflows already present in the product, then expands monetisation, network effects and data intelligence.
Reliability, UX, QA, analytics, performance and source-level architecture.
First paid users, pricing tests, contractor pilots, retention and acquisition measurement.
Independent contractor participation, project matching, claims and structured project administration.
State-based rate intelligence, larger structured project datasets and increasingly useful decision support.
Structure, infrastructure, security, analytics and product hardening.
First paid users, pilots, pricing and acquisition experiments.
Retention, contractor network and measurable unit economics.
Team expansion, broader network and data-driven product growth.
Indicative 12-month planning case. Allocation remains subject to final investment structure and diligence.
Founder/MD planning compensation plus hiring envelope to reduce founder dependency.
Hardening, UX/QA, reliability, feature delivery and commercial productisation.
Customer acquisition, partnerships, campaigns and monetisation validation.
Infrastructure, security, operations and appropriate corporate/IP/governance work.
The founder combines construction/project experience, quantity-surveying and costing logic, design and software development. TERAJUWORKS has been built in-house from product concept and interface through frontend, backend, data architecture and project-control workflows.
The investment case is specifically intended to convert that founder-led capability into a scalable team, formal technology venture and repeatable commercial operation.
View corporate profile →The repository contains the active product interfaces, API infrastructure, admin controls, calculation engine, AI floor-plan workflow, local-first IFC import bridge, contractor/rate infrastructure and project-control workflow.
TERAJUWORKS as a technology venture: software, product, technology team, commercialisation, IP and scalable growth. It is not an investment into the general construction operations of TERAJU CIPTABINA RESOURCES.
No. The current investor position is early commercial validation with 0 paying TERAJUWORKS software customers disclosed. The opportunity is to validate monetisation and repeatable acquisition from an existing working product base.
The current IFC Room / Area import bridge is designed local-first: the IFC file is stored in browser IndexedDB and room/area extraction is performed in the browser. The product explicitly states that IFC/room data is not sent to the server/database through that import flow.
Yes. TERAJU CIPTABINA RESOURCES can be a customer and contractor within the ecosystem, but the relationship should be documented as a related-party commercial relationship as the technology venture is formalised.
Paid conversion, retention, contractor subscription demand, acquisition economics, independent network activity, scalable support and the commercial value of the structured construction-data layer.
For investors and technology partners, the next step is a product walkthrough and discussion of the investment structure, commercial model and scaling plan.
TERAJU CIPTABINA RESOURCES · Malaysia