We build your website and give your staff one place for researcher profiles, grant applications, projects and reports. Less repeated data entry. Fewer updates and approvals to chase by email.
We implement the website and software around your institution’s people and processes. Start with a department or faculty, then add the workflows your staff need.
We build your institution’s website. Researchers submit updates to their people and research pages; editors review and publish them.
Give staff a place to maintain research records, submit requests and follow approvals, instead of passing every update between forms and inboxes.
Describe a research question. SciMatch helps you find relevant researchers and inspect their publications before approaching a potential collaborator.
Discover funding calls, prepare applications, track internal decisions and carry an awarded grant into project reporting. Keep its context with the work.
Browse the capabilities, find the processes you care about, and see what we’re building next.
Free for the university, in exchange for agreed research data powering the network. We scope the first unit, records, workflows, access, and rollout with you.
How implementation worksOne foundation. Different ways to make the working day easier.
Keep the record of your work connected to the opportunities and projects that come next.
Review imported authorship and correct uncertain attribution.
Prepare your expertise and biography for editorial review.
Review a funding call and investigate complementary expertise.
Connect activity, outputs, and progress to the project record.
Review the source and attribution, confirm the correct researcher, then submit the public record for review.
A reviewed publication connected to the right person, with its source retained.
Public updates follow the institution’s review process. Private project work stays within its access controls.
Explore how the pieces fit together.
The work keeps its context as it moves.
A public website and a shared home for people, publications, and projects. Maintain the information once, then put it to work across your research activity.
Different institutions shouldn’t have to pretend they’re the same department. Your identity, people, roles, and approval paths shape the implementation.
One unit. Its own website, people, research records, and workflows. A focused place to begin.
A practical rollout plan for your department, agreed before onboarding. Existing systems, export quality and institutional rules shape the work.
Map the unit, its audiences, current systems and the first workflows worth connecting.
A coordinator, the people responsible for content and processes, and the priorities for the first unit.
A shared scope: records, workflows, responsibilities, data boundaries and acceptance criteria.
Review the available content and exports. Propose field mapping, source connections and a plan for uncertain or incomplete records.
Existing website content, agreed research records and available exports, with permission to use them.
A content and data map showing what to bring over, what needs review, and what remains outside the rollout.
Configure identity, navigation, roles and the agreed workflows. Walk through representative publishing, review and research tasks with your team.
Named editors and reviewers, confirmed institutional rules, and feedback on the trial workflows.
A reviewable first workspace and website, with agreed checks for public content, private access and handoffs.
Resolve the agreed launch checks, guide editors and researchers through their tasks, and plan the next scope with the coordinator.
Approval of the initial content and access setup, plus people who will own day-to-day updates.
An agreed launch and handover: operating responsibilities, outstanding items and a route for the next unit or workflow.
Start with a useful unit and a real workflow. Import coverage, launch checks and ongoing responsibilities are agreed explicitly; the plan does not assume every existing system can be migrated automatically.
We provide the software and implement it for your institution. In return, research data helps Scindu understand expertise and connect it with funding and business challenges.
We agree the data scope with you. Discoverability comes from curated research records; private applications and internal work need their own access boundaries.
See the business side of the connectionThe connected foundation opens up a more useful next layer. These capabilities are planned, with scope to shape them around institutional needs.
Yes. Start with the unit that needs it: a department, faculty, research centre, or university. The rollout is scoped around its website, people, existing processes, and institutional structure, with room to connect more units.
The university offer includes the software and its implementation. We map the initial scope together: public website, people and research records, grant and project workflows, and the processes your unit needs. The rollout and responsibilities are agreed before onboarding.
Research data is part of the exchange behind the free university offer. We agree what data supports discovery and collaboration. Public researcher and output records can make expertise discoverable; private proposals, award documents, and internal decisions belong in the institution’s permissioned workspace.
The workspace supports preparation, internal approval, submission records, funding outcomes, and project handoff. External submission follows the funding agency’s actual process. A submission record is not an automatic submission to an agency.